Aggregates and entities in Microservices - Architecture Diagram

System Overview - Aggregates and entities

This system demonstrates how aggregates and entities are organized within a microservices architecture. Aggregates group related entities to maintain consistency and transactional boundaries. The system ensures that each microservice manages its own aggregate root, coordinating entity changes internally while communicating with other services asynchronously.

Architecture Diagram

User
  |
  v
Load Balancer
  |
  v
API Gateway
  |
  +-------------------+-------------------+
  |                   |                   |
Order Service     Customer Service     Inventory Service
  |                   |                   |
Aggregate Root     Aggregate Root     Aggregate Root
(Order Aggregate)  (Customer Aggregate) (Inventory Aggregate)
  |                   |                   |
Entities           Entities           Entities
  |                   |                   |
Database           Database           Database
  |                   |                   |
Cache              Cache              Cache

Components

User

user

Initiates requests to the system

Load Balancer

load_balancer

Distributes incoming requests evenly across API Gateway instances

API Gateway

api_gateway

Routes requests to appropriate microservices and handles authentication

Order Service

service

Manages Order aggregate and its entities

Customer Service

service

Manages Customer aggregate and its entities

Inventory Service

service

Manages Inventory aggregate and its entities

Order Aggregate Root

aggregate_root

Ensures consistency and transactional boundary for Order entities

Customer Aggregate Root

aggregate_root

Ensures consistency and transactional boundary for Customer entities

Inventory Aggregate Root

aggregate_root

Ensures consistency and transactional boundary for Inventory entities

Database

database

Stores persistent data for each service

Cache

cache

Speeds up read operations by storing frequently accessed data

Request Flow - 10 Hops

User → Load Balancer

Load Balancer → API Gateway

API Gateway → Order Service

Order Service → Cache

Cache → Order Service

Order Service → Database

Database → Order Service

Order Service → Cache

Order Service → API Gateway

API Gateway → User

Failure Scenario

Component Fails:Database

Impact:Writes to aggregates fail, but reads may succeed if cache has data. Data consistency risks increase.

Mitigation:Use database replication and failover to restore availability. Cache serves stale reads temporarily.

Architecture Quiz - 3 Questions

Which component ensures transactional consistency within an aggregate?

A Aggregate Root

B API Gateway

C Load Balancer

D Cache

Design Principle

This architecture demonstrates the principle of aggregate roots as transactional boundaries within microservices. Each service manages its own aggregate and entities to maintain consistency. Caches improve read performance, while API Gateway and load balancer ensure proper routing and scalability.

Practice

1. In microservices, what is the main role of an aggregate root entity?

easy

A. It acts as a database for all microservices.

B. It stores unrelated data from different services.

C. It handles user interface rendering.

D. It controls all changes within the aggregate to keep data consistent.

Solution

1. Step 1: Understand aggregate root responsibility

   The aggregate root is the main entity that manages all changes inside its aggregate to ensure consistency.

2. Step 2: Eliminate unrelated options

   Options A, B, and D describe roles unrelated to aggregate roots in microservices.

3. Final Answer:

   It controls all changes within the aggregate to keep data consistent. -> Option D

4. Quick Check:

   Aggregate root controls changes = C [OK]

Hint: Aggregate root manages changes inside its group [OK]

Common Mistakes:

• Confusing aggregate root with database or UI component
• Thinking aggregate root stores unrelated data
• Assuming aggregate root handles external service data

2. Which of the following correctly represents an aggregate in a microservice domain model?

easy

A. Order (root) -> OrderItems (entities) -> PaymentDetails (entity)

B. OrderItems (root) -> Order -> PaymentDetails

C. PaymentDetails (root) -> Order -> OrderItems

D. Order -> PaymentDetails -> OrderItems (all roots)

Solution

1. Step 1: Identify the aggregate root

   In an order system, the Order is the root entity controlling related entities like OrderItems and PaymentDetails.

2. Step 2: Check the hierarchy correctness

   Order (root) -> OrderItems (entities) -> PaymentDetails (entity) shows Order as root with related entities under it, which is correct. Other options misplace roots or treat all as roots.

3. Final Answer:

   Order (root) -> OrderItems (entities) -> PaymentDetails (entity) -> Option A

4. Quick Check:

   Root entity is Order controlling others = A [OK]

Hint: Root entity leads related entities in aggregate [OK]

Common Mistakes:

• Assigning wrong entity as root
• Treating all entities as roots
• Ignoring aggregate boundaries

3. Given the aggregate root Customer with entities Address and Order, which operation should only be performed through Customer?

medium

A. Deleting Order independently from Customer

B. Directly updating an Order without Customer involvement

C. Adding a new Address via the Customer aggregate root

D. Querying Order data directly from the database

Solution

1. Step 1: Understand aggregate root control

   The aggregate root Customer controls all changes to its entities like Address and Order to maintain consistency.

2. Step 2: Identify allowed operations

   Adding a new Address should go through Customer. Direct updates or deletes bypassing root break consistency.

3. Final Answer:

   Adding a new Address via the Customer aggregate root -> Option C

4. Quick Check:

   Changes go through root entity = A [OK]

Hint: All changes pass through aggregate root only [OK]

Common Mistakes:

• Updating entities directly without root
• Deleting entities independently
• Confusing querying with updating

4. You have a microservice with an aggregate root Invoice and entities LineItem. The code allows direct modification of LineItem without Invoice. What is the main problem?

medium

A. Performance will improve due to direct access.

B. Data consistency may break because changes bypass the aggregate root.

C. It will reduce network calls between services.

D. It simplifies the codebase without side effects.

Solution

1. Step 1: Identify aggregate root role in consistency

   The aggregate root Invoice ensures all changes to LineItem are consistent and valid.

2. Step 2: Analyze direct modification impact

   Directly modifying LineItem bypasses Invoice, risking inconsistent or invalid data.

3. Final Answer:

   Data consistency may break because changes bypass the aggregate root. -> Option B

4. Quick Check:

   Bypassing root risks consistency = B [OK]

Hint: Bypass root risks data consistency [OK]

Common Mistakes:

• Assuming direct access improves design
• Ignoring consistency importance
• Confusing performance with correctness

5. You design a microservice for a shopping cart system. The cart is an aggregate root with entities like CartItem and Discount. Which design choice best ensures data consistency and scalability?

hard

A. Make Cart the aggregate root controlling all CartItem and Discount changes.

B. Use a single database table for Cart, CartItem, and Discount without aggregates.

C. Store CartItem and Discount in separate microservices with no coordination.

D. Allow CartItem and Discount to be updated independently without Cart involvement.

Solution

1. Step 1: Apply aggregate root principle for consistency

   Cart as aggregate root should control all changes to CartItem and Discount to keep data consistent.

2. Step 2: Consider scalability and design best practices

   Centralizing changes through Cart allows easier management and scaling of the microservice without data conflicts.

3. Step 3: Evaluate other options

   Options A and C risk inconsistency; B ignores aggregate design and can cause complexity.

4. Final Answer:

   Make Cart the aggregate root controlling all CartItem and Discount changes. -> Option A

5. Quick Check:

   Aggregate root controls changes for consistency and scale = D [OK]

Hint: Aggregate root controls related entities for consistency and scale [OK]

Common Mistakes:

• Allowing independent updates breaking consistency
• Splitting tightly coupled entities into separate services
• Ignoring aggregate design principles