Event-driven microservices architecture consists of interconnected microservices that communicate based on triggered events. Key aspects include leveraging managed cloud services, event sourcing, and command query responsibility segregation (CQRS) for scalability and fault isolation, while also addressing challenges like event ordering and state management. Tools such as RabbitMQ and Amazon EventBridge facilitate the implementation of this architecture.

1. #techtuesdays

2. Definition of Event Driven
Microservices Architecture
Event driven microservices architecture is
an array of microservices representing a
complex system where those
communicate with each other when an
event is triggered.
#techtuesdays

3. Tips to Plan an Event Driven
Architecture
#techtuesdays
Leverage managed cloud services
Build microservices catering to specific
business needs
Integrate relatable business functionalities to
existing microservices
Maintain catalog for event streams and
services

4. Patterns of Event Driven
Microservices Architecture
#techtuesdays
Event streaming
Event sourcing
Polyglot persistence
Command and Query Responsibility
Segregation

5. Best Practices for Designing
Event Driven Microservices
#techtuesdays
Event Sourcing and CQRS
Asynchronous Communication Patterns
Use event sourcing to capture and store all changes to an application's
state, enabling auditing, debugging, and better scalability. Combine
with Command Query Responsibility Segregation (CQRS) for efficient
data retrieval.
Use message queues and publish/subscribe models to enable loose
coupling, improve scalability, and ensure reliable message delivery

6. Benefits of Event Driven
Microservices
#techtuesdays
Increased Scalability Improved Fault Isolation
Services can be scaled
independently, allowing for
better resource utilization and
handling of varying workloads.
Failures in one microservice
can be isolated, preventing
cascading failures and
minimizing impact on the
entire system.

7. Challenges of Implementing
Event Driven Microservices
#techtuesdays
Handling Event Ordering and Consistency
Managing Distributed State
Ensuring events are processed in the correct order and
maintaining data consistency across services can be complex.
Coordinating state changes across multiple services requires
careful design to avoid data inconsistencies.

8. Event Driven Microservices
Architecture Tools
#techtuesdays
Open source Event
streaming software.
A message broker
that supports
multiple protocols
including MQTT,
AMQP, and STOMP.
Reacts to events
from SaaS
applications based
on a predefined
schema for events.
Allows for
continuous data
analysis.
RabbitMQ
Amazon
EventBridge

9. Thank you for
your time.
#techtuesdays www.Gleecus.com
hello@gleecus.com
Contact us: