Domain Driven Design Microservices Io
From domain driven design ddd.
Domain driven design microservices io. I love software books that are both old and still relevant. When in doubt start with more coarse grained microservices. These events might be needed for example to update a cqrs view alternatively the service might participate in an choreography based saga which uses events for coordination.
Stack overflow for teams is a private secure spot for you and your coworkers to find and share information. Microservices io is brought to you by chris richardson. A domain model entity implements behaviors through methods that is it s not an anemic model.
A service often needs to publish events when it updates its data. Above all it s important to be pragmatic and remember that domain driven design is an iterative process. Chris is the creator of microservices io.
Chapter 2 talks in detail about how a domain is divided into bounded contexts and chapter 3 is the best source on drawing context maps. Splitting a microservice into two smaller services is easier than refactoring functionality across several existing microservices. A useful guideline from object oriented design ood.
Example of a domain entity design implementing data plus behavior. Sometimes a bc could be composed of several physical services but not vice versa. Figure 7 8 shows a domain entity that implements not only data attributes but operations or methods with related domain logic.
Ddd refers to the application s problem space the business as the domain. Define services corresponding to domain driven design ddd subdomains. A domain is consists of multiple subdomains.