In this video, learn how to fix the problems uncovered in the last session by using a reactive, event-based system that does the same work.
- [Instructor] The other way to organize … your system of services is by using choreography … or reactive systems. … In a sense choreography is a solution … to the problems that we were just talking about … when we were looking at the declarative systems. … Now, this is where we start, with our synchronous services … that knew about downstreamed things. … What happens if we replace those declarative APIs … with generic ones? … In other words, now instead of the shopping cart service … telling the billing, and warehouse, and email services … what to do, the shopping cart service just announces … to the world a new order has been placed … if you're interested in that do something about it. … The billing service will be sitting around waiting … for that message to be generated. … And it says, oh a new order has been placed … I better send the bill. … And the warehouse service says, oh a new order … has been placed I better ship it out. … And the email service says, oh a new order … has been placed I better notify my customer. …
- How DDD differs from other architectural approaches
- How DDD fits with agile
- Advantages of microservices
- Bounded contexts and entities
- Reactive vs. declarative systems
- Using event storming to develop a DDD architecture