Özer Cem KELAHMETKELAHMET
Glossary · MLOps and AI infrastructure

What is Domain-driven design? Definition and meaning

A design approach that uses a shared language and bounded contexts to align code with the business.

Definition

Domain-driven design: A design approach that uses a shared language and bounded contexts to align code with the business.

In short: Modelling software around the business domain.

When it is used

Complex business systems.

Where it fits

Domain-driven design belongs to Architecture in the MLOps and AI infrastructure topic. These are the other terms in the same group:

  • Microservices: An architecture that splits a system into services that are deployed and scaled separately.
  • CQRS: Command query responsibility segregation uses separate models for updating and querying data.
  • Event sourcing: Persists every state change as an immutable event, from which current state is rebuilt.
  • Hexagonal architecture: Isolates business logic from infrastructure through explicit ports and adapters.
  • Saga pattern: Splits a business transaction into local steps, each with a compensating action if later steps fail.
  • Circuit breaker: Opens after repeated failures so a service fails fast and recovers, instead of piling up requests.
  • gRPC: A framework that uses Protocol Buffers and HTTP/2 for typed, efficient service calls.
  • GraphQL: An API style in which clients ask for exactly the fields they need in one request.

Learn more

The full guide to Domain-driven design explains how it works, when to use it and how it compares with the alternatives, with examples. The glossary lists every term on the site from A to Z.

Previous term: Domain adaptation · Next term: DoRA

Last updated Nov 18, 2026
Type to search.
    ↑↓ navigate↵ open