Summary
We started the chapter with an overview of what microservices are and how they pertain to DDD for you to understand their relationship. We also looked at the benefits and challenges of microservices as compared to DDD.
Later, we learned how DDD relates to the characteristics of microservices and that teams need to be aligned to a service, ideally a one-to-one team alignment to a microservice. Each service should have its own code base managed by one team. We learned that we need to take a holistic view of our microservices architecture. We also discussed the Cynefin framework to determine the type of problem we are trying to solve, in order to understand the amount of effort and resources required to build our microservices.
We talked about how each boundary is based on a logical grouping of aggregates that are transaction boundaries and enforce invariants of the domain. We learned that we may not get this right first time and, as our knowledge of the domain deepens...
