Event Driven Architecture

In a microservices architecture implemented with Domain-Driven Design (DDD), it is often necessary to connect multiple bounded contexts.

We would avoid synchronous API calls, which can result in tight coupling between the contexts. To address these challenges, we propose using an event-driven architecture to connect the different bounded contexts. With this approach, each bounded context can publish integration events that reflect changes in its state, which other contexts can subscribe to and react accordingly.

This creates a decoupled architecture, allowing the different contexts to evolve independently while ensuring consistency and data integrity across the system.

See this notion page to read about event-driven architecture patterns.