Introduction to Event Sourcing Workshop
Event Sourcing is perceived as a complex pattern. Some believe that it's like Nessie, everyone's heard about it, but rarely seen it. In fact, Event Sourcing is a pretty practical and straightforward concept. It helps build predictable applications closer to business. Nowadays, storage is cheap, and information is priceless. In Event Sourcing, no data is lost.
The workshop aims to build the knowledge of the general concept and its related patterns for the participants. The acquired knowledge will allow for the conscious design of architectural solutions and the analysis of associated risks.
The emphasis will be on a pragmatic understanding of architectures and applying it in practice using Marten and EventStoreDB.
- Introduction to Event-Driven Architectures. Differences from the classical approach are foundations and terminology (event, event streams, command, query).
- What is Event Sourcing, and how is it different from Event Streaming. Advantages and disadvantages.
- Write model, data consistency guarantees on examples from Marten and EventStoreDB.
- Various ways of handling business logic: Aggregates, Command Handlers, functional approach.
- Projections, best practices and concerns for building read models from events on the examples from Marten and EventStoreDB.
- Challenges in Event Sourcing and EDA: deliverability guarantees, sequence of event handling, idempotency, etc.
- Saga, Choreography, Process Manager, distributed processes in practice.
- Event Sourcing in the context of application architecture, integration with other approaches (CQRS, microservices, messaging, etc.).
- Good and bad practices in event modelling.
- Event Sourcing on production, evolution, events' schema versioning, etc.
You can do the workshop as a self-paced kit. That should give you a good foundation for starting your journey with Event Sourcing and learning tools like Marten and EventStoreDB. If you'd like to get full coverage with all nuances of the private workshop, feel free to contact me via email.
Read also more in my article Introduction to Event Sourcing - Self Paced Kit.
Exercises
Follow the instructions in exercises folders.
- Events definition.
- Getting State from events.
- Appending Events:
- Getting State from events
- Business logic:
- Optimistic Concurrency:
- Projections:
Prerequisites
- Install git - https://git-scm.com/downloads.
- Clone this repository.
- Install Node.js 18 - https://Node.js.org/en/download/ (Or better using NVM).
- Install VSCode, WebStorm or other prefered IDE.
- Install docker - https://docs.docker.com/engine/install/.
- Open the current folder in IDE.
Setup
- Install NPM packages by running:
npm install
. - Build source codes:
npm run build
. - If you're using VSCode, you may consider importing profile from the ./.vscode/Node.js.code-profile to get all recommended plugins.
Ensuring that all is setup correctly
- Run:
docker-compose up
to start EventStoreDB docker image. - Run
npm run test:solved
. If all is fine then all tests should be green.
Running
- Run:
docker-compose up
to start EventStoreDB docker image.You should automatically get EventStoreDB UI: http://localhost:2113/ - You can get build watch by running
npm run build:ts:watch
. - To run test for exercises run
npm run test:exercise
. For solutions runnpm run test:solved
, for allnpm run test
. - Whe you're working with exercise and want to have tests running on file change run
npm run test:exercise:watch
.