EDA refresh
I'm working on the Event Driven Architecture reference implementation for IBM Architecture center. The working public content is in this GitHub repository: https://github.com/ibm-cloud-architecture/refarch-eda.
Event Driven Architecture is a pattern of application deployment that was created at least 20 years ago and is used by a lot of companies. With hybrid cloud-native implementation and microservices adoption, EDA gets a new focus by helping to address the loosely coupling requirements of microservices and avoid complex communication integration. The adoption of pub/sub communication model, Event Sourcing, CQRS and Saga patterns helps to implement microservices to support high scalability and resiliency for cloud deployment. EDA is becoming a mandatory approach for agile architecture and opens the opportunity to add artificial intelligent services to process real-time event, and process event streams to derive real-time analytics. We are addressing all those practices in detail in the architecture center, complemented by the event storming methodology practice to model events, aggregates and service boundary and illustrated with a concrete example as part of a reference implementation.
Event Driven Architecture is a pattern of application deployment that was created at least 20 years ago and is used by a lot of companies. With hybrid cloud-native implementation and microservices adoption, EDA gets a new focus by helping to address the loosely coupling requirements of microservices and avoid complex communication integration. The adoption of pub/sub communication model, Event Sourcing, CQRS and Saga patterns helps to implement microservices to support high scalability and resiliency for cloud deployment. EDA is becoming a mandatory approach for agile architecture and opens the opportunity to add artificial intelligent services to process real-time event, and process event streams to derive real-time analytics. We are addressing all those practices in detail in the architecture center, complemented by the event storming methodology practice to model events, aggregates and service boundary and illustrated with a concrete example as part of a reference implementation.
Comments