Using the Event-Driven Approach in Microservice Architecture
This is an intensive, 2-day workshop (≈ 80% hands-on, 20% theory) that introduces event-driven systems—from the fundamentals, through design patterns, to migrating from synchronous architectures.
Ideal for teams that…
Solid backend and architecture — patterns proven in production.
Understand the fundamentals of event-driven architecture (EDA) and how it’s used in practice
Learn to design scalable, fault-tolerant distributed systems
Get to know tools, patterns, and techniques needed to implement EDA in production environments
Gain hands-on experience modeling processes using Event Storming
What we actually do
- · Introduction to event-driven architecture (EDA) Key concepts and principles of EDA Benefits and challenges of using an event-driven approach Applying the CAP theorem in practice
- · Comparing synchronous and asynchronous integration Pros and cons of both approaches Use-case scenarios How to choose the right approach depending on the business context
- · Core concepts and terminology in event-driven systems Idempotency Command vs event Distributed transaction Sagas: choreography vs orchestration Message delivery guarantees (at-most-once, at-least-once, exactly-once) Data consistency and eventual consistency CQRS and read models Schema versioning for messages
- · Designing and implementing event-driven solutions Choosing suitable technologies Creating and managing events Error handling and monitoring of events Patterns for event processing
- · Monitoring and metrics in event-driven systems Ways to build metrics to track business processes – tools and techniques for monitoring Detecting and responding to problems in event streams
From brief to retro in 30 days.
Brief & diagnosis
A call with the team lead + a short survey for participants. We define goals, gap and context.
Program customization
We adapt modules, case studies and code examples to your stack. Approval in 5 days.
Workshop
Trainer-led sessions, hands-on, code review. Mentor available between sessions too.
Retro + report
Outcome report for the team and lead. 30 days of consulting included.
Send a brief. We'll reply within 1 day.
After a short brief we'll prepare a program and a quote. No obligations — it's just a starting point.
Thank you!
We'll get back to you within 1 business day.
Other programs for teams
See all →Application architecture
Solid backend and architecture — patterns proven in production.
DDD
Solid backend and architecture — patterns proven in production.
Design patterns in C#
Solid backend and architecture — patterns proven in production.