is the most effective way to learn Event Sourcing and Event-Driven Architectures. I designed two workshops that should give you good foundations and a set of skills for a practical and pragmatic start to your journey.
You’ll understand the best practices and tradeoffs, being ready to apply them to your project.
Want to have the training in your company? Have any questions or want custom one?
I perfectly remember how I started my journey with Event-Driven Architecture and Event Sourcing. I was banging my head against the wall. I thought it was pointless. However, I was stubborn, and it turned out that it was not as difficult as painting it.
The main reason is the lack of decent practical learning materials. For several years I have been trying to cover it up by documenting and sharing my path and the knowledge I have gained.
Now you also have the opportunity to take advantage of it! Without hitting your head against a wall.
I run trainings both online and offline in the office.
🛠️ Description: Event Sourcing allows you to create business-related applications. Recording events (facts) about the business process gives a complete understanding of your workflow and reflects them in the code. It is wrongly considered a complicated pattern that is challenging to apply in practice. The workshop will be hands-on and teach you how to use Event Sourcing, giving you solid foundations. Exercises will be run in C#, Java or NodeJS.
- Good understanding of all the building blocks of Event Sourcing,
- When and how to use it and what benefits it brings,
- How to reflect your business logic in the code using events,
- Differences to the classical approach,
- Different tools such as Marten and EventStoreDB and the differences between them,
- How to use Event Sourcing on your system,
- Challenges related to Event Sourcing and recommended solutions.
⏱️ Length: 2-3 days
- Introduction to Event Sourcing. Basic terminology (event, stream of events, command), differences from the classical approach.
- What is Event Sourcing, and how is it different from Event Streaming. Advantages and disadvantages.
- Write model and data consistency guarantees.
- Various ways of handling business logic: Aggregates, Command Handlers, functional approach.
- Projections and best practices for building read models.
- Challenges in Event Sourcing and EDA: delivery guarantees, event processing order, idempotency, etc.
- Saga, Choreography, Process Manager, handling distributed processes.
- Event Sourcing in the context of application architecture, integration with other approaches.
- Good and bad practices in modelling and handling events.
- Event Sourcing on production, evolution, event versioning, etc.
🛠️ Description: Event-driven architectures help build predictable, scalable, and fault-tolerant systems. In addition, they improve both the technical autonomy of created systems and the teams working on them. However, like any architecture, it has distinctive features that can cause far-reaching complications if not understood well.
🧑🎓 Outcomes: The training aims to build the knowledge of the general concept and its patterns for the participants. The emphasis will be on a pragmatic understanding of architectures and tools rather than specific implementations. The acquired knowledge will allow for the conscious design of architectural solutions and the analysis of related risks. You’ll also learn how tools like RabbitMQ, Kafka, and Cloud-Native messaging systems differ and how selecting them can impact your architecture.
Additionally, the training will include a workshop part (in the form of a team “Architecture Kata”), where you will practice your theoretical knowledge. The training involves:
- Interaction and discussion with participants.
- Exchanging views.
- Asking questions based on current problems.
⏱️ Length: 2-3 days
- Introduction and basic concepts (events, commands, business flows).
- Comparison with the classical approach of synchronous communication.
- Message delivery guarantees: how to ensure reliable communication between services.
- Messaging idempotency: what to do when we get messages more than once.
- The order of events, why is it essential, and when you can live without it.
- Types of data consistency: Strong, Eventual, Causal Consistency.
- CQRS, facts and myths, why it is useful.
- Projections and how to create read models based on events.
- Distributed transactions versus patterns such as Saga, Process Manager, Choreography.
- Auditability, metrics, tracing.
- Basics of Event Sourcing.
- How (not) to model events.
- Migration (versioning) of the event schema.
- Ways of transforming/migrating from systems based on synchronous communication to architectures based on events.