ภาษาร่วมและแบบจำลองโดเมน

Software fails when developers and domain experts speak different languages. A developer says 'record', the expert says 'invoice', and subtle meaning is lost in translation.

Domain-Driven Design closes this gap with a shared vocabulary baked into the code.

The ubiquitous language is a single, shared vocabulary used by everyone — business and engineering — in conversation, documentation, and code.

If the business calls it a 'Subscription', the class is named Subscription, not UserPlanRecord.

The point is that the language is reflected directly in the model. Method and class names mirror how experts speak.

An anemic model is just data with no behavior; logic leaks into services. A rich domain model puts behavior and rules inside the objects that own the data.

DDD favors rich models that protect their own invariants.

An entity has a distinct identity that persists over time, even as its attributes change. A customer is the same customer after changing their email.

Entities are compared by ID, not by their field values.

A value object has no identity and is defined entirely by its attributes. Money, a date range, or an address are value objects.

Two value objects with the same values are interchangeable, and they should be immutable.

An invariant is a rule that must always hold true, such as 'an order total can never be negative'. The domain model enforces invariants so invalid states are impossible.

Validation lives inside the model, not scattered across the app.

Some logic does not naturally belong to a single entity. A domain service holds such operations, like transferring funds between two accounts.

Domain services are named in the ubiquitous language too, expressing business actions.

A repository provides the illusion of an in-memory collection of domain objects, hiding the database details.

The domain talks to subscriptions.findById() without knowing about SQL or tables.

The ubiquitous language evolves. As understanding deepens, terms change — and the code must change with them. Renaming is a feature, not a chore.

A model that drifts from how the business speaks becomes a liability.

SaaS domains (billing, subscriptions, entitlements) are complex and ever-changing. A clear domain model and shared language let teams reason about, extend, and refactor the system with confidence.

It turns business rules into first-class, maintainable code.

Test your DDD modeling knowledge.

You learned core DDD building blocks:

• Ubiquitous language shared by business and code
• Rich models with entities, value objects, and enforced invariants
• Domain services and repositories

Together they keep complex SaaS domains aligned with the business.