Domain Driven Design Gateway

This approach would require the application gateway to interact with multiple bounded contexts which seems like it may violate ddd in some way.

Domain driven design gateway. It may not be well suited for a microservice. Domain driven design is a framework based on strategic value and it s about mapping business domain concepts into software artifacts. Strategic ddd helps to ensure that your architecture remains focused on business capabilities.

In other words you can have any kind of client for the domain layer in any architecture. The patterns are described in more detail in chapters 5 6 of eric evans book and in implementing domain driven design by vaughn vernon. Software should be like.

Ddd has two distinct phases strategic and tactical. Tactical ddd provides a set of design patterns. Domain driven design object orientation done right but everything from tool choice to the halting problem to the pointy haired boss constrains and shapes the software you create.

The domain model also provides the language and context. For example in a banking application customers and accounts would be entities. In strategic ddd you are defining the large scale structure of the system.

Any microservice implementation could benefit by following. An entity has a unique identifier in the system which can be used to look up or retrieve. In the context of building applications ddd talks about problems as domains.

Domain driven design is a key element of soa architecture because it helps in encapsulating the business logic and rules in domain objects. Ddd requires a good understanding of the domain for which the application will be written. It also suggests many technical concepts and patterns like domain entities with rich models no.