Webinar
Keep your streams short! Or how to model event-sourced systems efficiently
Presenter: Oskar Dudycz | Duration: 1 hour 35 minutes
In event-sourced systems, no data is lost. We record new facts after each business operation. That's a huge benefit but also a challenge. At some point, we realise that we have too many events in our streams. That causes a whole variety of issues: operational, performance, versioning, but also cognitive load and blurring the entire picture. In this talk, you'll learn:
- How to deal with the temporal aspect of our system and why it's essential to keep your streams short.
- Strategies and techniques to model your domain into streams efficiently.
- How to efficiently create and maintain your event-sourced system, avoiding common pitfalls.
If you have any questions about the content covered in this webinar, please feel free to ask them on the Event Store community forum.
-
Perhaps you’re new to Event Sourcing. Or maybe you know what it is, but are unsure how best to harness its power. In either case, this webinar with Matt Macchia will help you gain the confidence to get started.
Watch video - EventStoreDB is the database built for Event Sourcing, but what does this actually mean? How does its underlying data model make it different? And what are its superpowers? Stephen Tung explains what EventStoreDB is and how it can help your business. Watch video
New to Event Sourcing?
-
New to Event Sourcing and need an overview of the key concepts? Our Beginner's Guide to Event Sourcing is a great place to start and includes diagrams and code snippets to help explain things. -
Beginner's Guide to CQRS
Read time: 10 minutesCQRS is an architectural pattern acronym, standing for Command Query Responsibility Segregation. It divides a system’s actions into commands and queries. This guide explains the benefits of CQRS and its core principles, as well as some misconceptions around the pattern. -
Beginner's Guide to Event-Driven Architecture
Read time: 10 minutesEvent-driven architecture is a software architecture paradigm that considers the individual messages of a network of services to be events, rather than requests. Read more in our beginner's guide.