Tools
- Miro Event Modeling Toolkit: Build event-driven systems with visual Event Modeling directly in Miro. Design, collaborate, and generate code from your event models.
Reading
Articles/Blogs/Essays
"The Laws of Event Sourcing" - Real World Event Sourcing
- All Events are Immutable and Past Tense
- Applying a Failure Event Must Always Return the Previous State
- All Data Required for a Project Must Be on the Events
- Work Is a Side Effect
- All Projects must Stem from Events
- Never Manage More than One Flow per Process Manager
- Process Managers Must Not Read from Projections
- Event Schemas Are Immutable
- Different Projectors Cannot Share Projections
- Never Test Internal State
Rahul Krishnan's blog:
Oskar Dudycz's blog:
- How Postgres sequences issues can impact your messaging guarantees: Since Postgres BIGSERIAL column types can't ensure they're always bumped in exact transactional order (one transaction may run slower than others), it creates problems in event-driven models, where order is key.
- On rebuilding read models, Dead-Letter Queues and Why Letting Go is Sometimes the Answer
- Rebuilding Event-Driven Read Models in a safe and resilient way
- Multi-tenancy and dynamic messaging workload distribution
- Checkpointing the message processing
- Consumers, projectors, reactors and all that messaging jazz in Emmett
- Requeuing Roulette in Event-Driven Architecture and Messaging
- Handling Events Coming in an Unknown Order
- Dealing with Race Conditions in Event-Driven Architecture with Read Models
- How to build MongoDB Event Store
- Idempotent Command Handling
- Using event metadata in event-driven projections
- Writing and testing event-driven projections with Emmett, Pongo and PostgreSQL
- Combining the To-Do List and the Passage Of Time patterns for resilient business workflows
- How to build an in-memory Message Bus in TypeScript
- Event modelling anti-patterns explained
- I'm no longer Marten maintainer
- Testing Event Sourcing, Emmett edition
- Join my Event Sourcing workshops at Techorama and DDD Europe and speed up your journey!
- Should you always keep streams short in Event Sourcing?
- Implementing Closing the Books pattern
- Announcing Emmett! Take your event-driven applications back to the future!
- Production-Grade Event Sourcing Workshop - Modelling, DevOps, Process
- How TypeScript can help in modelling business workflows
- Stream ids, event types prefixes and other event data you might not want to slice off
- Should you record multiple events from business logic?
- Hitchhiker's Guide To Moving From Relational Data To Events
- Anti-patterns in event modelling - Clickbait event
- Oops I did it again, or how to update past data in Event Sourcing
- My journey from Aggregates to Functional Composition
- Event transformations, a tool to keep our processes loosely coupled
- Prototyping, an underestimated design skill
- Could you help me by filling a short survey about an online course?
- Recap of Event Sourcing Live 2023
- The Holy Grail syndrome
- Anti-patterns in event modelling - I'll just add one more field
- Is the audit log a proper architecture driver for Event Sourcing?
- General strategy for migrating relational data to document-based
- How to test event-driven projections
- Publishing read model changes from Marten
- Event stores are key-value databases, and why that matters
- Ensuring uniqueness in Marten event store
- Projecting Marten events to Elasticsearch
- How to handle multiple commands in the same transaction
- Set up OpenTelemetry with Event Sourcing and Marten
- Event-driven projections in Marten explained
- Guide to Projections and Read Models in Event-Driven Architecture
- How to validate business logic
- Let's build event store in one hour!
- Explicit events serialisation in Event Sourcing
- The magic is that there is no magic. Or how to understand design patterns.
- Share your story on Event Sourcing Live 2023
- Mapping event type by convention
- Never Lose Data Again - Event Sourcing to the Rescue!
- Testing business logic in Event Sourcing, and beyond!
- Event Versioning with Marten
- Slim your aggregates with Event Sourcing!
- Straightforward Event Sourcing with TypeScript and NodeJS
- Union types in C#
- How to effectively compose your business logic
- Event-driven distributed processes by example
- Should you throw an exception when rebuilding the state from events?
- Persistent vs catch-up, EventStoreDB subscriptions in action
- How to build a simple event pipeline
- Are Temporal Tables an alternative to Event Sourcing?
- Introduction to Event Sourcing - Self Paced Kit
- How to ensure uniqueness in Event Sourcing
- A simple trick for idempotency handling in the Elastic Search read model
- Using strongly-typed identifiers with Marten
- Integrating Marten with other systems
- How to do snapshots in Marten?
- Simple patterns for events schema versioning
- Let's talk about positions in event stores
- How to build event-driven projections with Entity Framework
- Anti-patterns in event modelling - State Obsession
- Anti-patterns in event modelling - Property Sourcing
- How to get the current entity state from events?
- When not to use Event Sourcing?
- How to scale projections in the event-driven systems?
- How using events helps in a teams' autonomy
- Events should be as small as possible, right?
- How to create projections of events for nested object structures?
- What's the difference between a command and an event?
- What if I told you that Relational Databases are in fact Event Stores?
- What texting your Ex has to do with Event-Driven Design?
- How to (not) do the events versioning?
- Why a bank account is not the best example of Event Sourcing?
- Revolution now!
Complex Event Processing (CEP)
Tags:
architecture
events
Last modified 17 February 2026