Domain-driven design

As explained in Automating API Delivery

Domain-driven design is an approach to software design that centers the structure and language of software on the underlying business domain.

Domain-driven design (DDD) centers software structure and language on a rich understanding of the business domain. It produces a domain model of business concepts, relationships, and workflows, then embeds a shared, rigorous ubiquitous language into the system. section 5.1

Apply DDD to API design by:

• Modeling business operations and data from user stories, job stories, user journeys, and the domain model. section 5.1
• Reviewing the model against the correct bounded context and principles such as single responsibility and encapsulation. section 5.1
• Translating the agreed API model and operations into OpenAPI changes guided by the organization’s API style guide. section 5.1

Figure 5.1 API reviews happen at the design stage of your APIOps workflow. API reviews start after the automated checks all pass. The API review is completed when all review comments have been resolved and the PR is merged.

Use the workflow view to place human API design review after automated checks and before pull-request merge. section 5.1

How Automating API Delivery covers it

How deep it goes

Defines domain models, ubiquitous language, and bounded contexts, then stops at conceptual API modeling and OpenAPI translation.

Examples

Uses business operations, data models, user journeys, and API model changes as design-review artifacts.

What it assumes

Assumes access to business-domain understanding and user or job stories while establishing shared terminology for software and domain experts.

What you can do after

Evaluate API models against bounded contexts and domain principles before implementing consistent API definitions.

How it connects

Connects domain models with ubiquitous language, bounded contexts, user stories, encapsulation, single responsibility, API design review, and OpenAPI.

liveBookmanning.com

Read Automating API Delivery on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Architecture Modernization: Socio-technical alignment of software, strategy, and structureDomain-driven design is a software design approach that models software around the concepts, rules, and boundaries of a business domain.
• 

  liveBookmanning.com
  Collaborative Software Design: How to facilitate domain modeling decisionsA software design approach that centers development on a model of the business domain and uses that model to guide software structure and implementation.
• 

  liveBookmanning.com
  Go in Action, Second EditionDomain-Driven Design is a software design approach that structures software around real-world business concepts and domain behavior.
• 

  liveBookmanning.com
  Effective Platform EngineeringDomain-driven design is a software design approach that centers the structure and behavior of software on the underlying business domain and its models.
• 

  liveBookmanning.com
  Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and TerraformDomain-driven design is a software design approach that models software around the concepts and boundaries of its problem domain.
• 

  liveBookmanning.com
  Functional Design and Architecture: Examples in HaskellDomain-driven design is a software development methodology that centers software design on the concepts, relationships, and rules of the problem domain.

Compare how 7 books explain domain-driven design →

Related concepts

• ubiquitous languageuses · Ubiquitous language is a shared, precise vocabulary that domain experts and software practitioners use consistently to describe a domain and its concepts.
• domain modeluses · A domain model is a software representation of the concepts, entities, relationships, rules, and behavior of a problem or business domain.
• microservice architectureuses · Microservice architecture is a software architectural style that organizes an application as independently deployable services with focused responsibilities that communicate through defined interfaces.
• complexityaddresses · Complexity is the degree of difficulty in understanding, analyzing, changing, or operating a system or problem, arising from its structure, behavior, or interacting parts.
• software design EventStorminguses · Software design EventStorming is a collaborative modeling technique that explores domain events and processes to inform software structure and behavior.

This explainer was generated by Manning's knowledge graph from the text of Automating API Delivery. The section links point to the parts of the book it draws on.