السياقات المحددة والتجميعات

Welcome to Domain-Driven Design (DDD)! This lesson explores how to manage complexity in large systems, especially SaaS applications, by defining clear boundaries.

As systems grow, understanding where one part of the business logic ends and another begins becomes crucial. DDD provides tools for this.

A Bounded Context is a central pattern in DDD. It defines a specific area within your overall domain where a particular model and its associated language are valid.

• Think of it as a conceptual boundary.
• Inside, terms have clear, unambiguous meanings.
• Outside, those same terms might mean something different.

Each Bounded Context has its own Ubiquitous Language. This is a shared language used by both domain experts and developers within that specific context.

For example, a 'Product' in an Inventory Management context might have properties like stockLevel and warehouseLocation. In a Marketing context, the same 'Product' might have campaignPrice and adCopy.

How do you find these boundaries in your SaaS application?

• Look for distinct business capabilities: e.g., Order Management, Customer Support, Billing.
• Identify different teams: Teams often organize around specific business areas.
• Spot ambiguous terms: If a word means different things to different people, you've likely found a context boundary.

Bounded Contexts are excellent candidates for defining microservice boundaries.

Typically, one Bounded Context maps to one microservice, or sometimes a few closely related microservices. This helps ensure that each service has a clear, cohesive responsibility and its own consistent model.

Within a Bounded Context, we need to ensure data consistency. This is where Aggregates come in.

An Aggregate is a cluster of domain objects that are treated as a single unit for data changes. It defines a transactional boundary around a group of related entities and value objects.

Every Aggregate has an Aggregate Root. This is a specific entity within the cluster that acts as the single entry point for all operations on the Aggregate.

• Clients only hold references to the Root.
• The Root is responsible for maintaining the consistency (invariants) of all objects within its Aggregate.

To maintain consistency, Aggregates follow strict rules:

• Only the Aggregate Root can be referenced from outside the Aggregate.
• Objects inside the Aggregate can reference each other.
• All changes within an Aggregate must be committed in a single transaction.
• Aggregates should be kept as small as possible to reduce contention and improve performance.

Consider an Order aggregate. The Order entity is the Aggregate Root. It contains OrderItem entities.

When you add an item to an order, you interact with the Order root, which then manages its OrderItems internally, ensuring the order's state remains consistent.

In this lesson, we explored two fundamental DDD patterns:

• Bounded Contexts: Define clear logical boundaries for your domain models, each with its own Ubiquitous Language. They are key for structuring microservices.
• Aggregates: Enforce transactional consistency within a Bounded Context by grouping related objects under an Aggregate Root, ensuring integrity during changes.

These patterns help build robust, understandable, and scalable SaaS applications.