Allard Buijze
CQRS and Event Sourcing without the pixie dust
#1about 3 minutes
The problem with traditional layered architectures
Traditional layered architectures often evolve into a "big ball of mud" monolith that is difficult to change and maintain.
#2about 3 minutes
Why microservices often become a distributed monolith
Applying monolithic development practices to microservices results in a distributed "big pile of mud" instead of a truly modular system.
#3about 6 minutes
Using events to decouple services in architecture
Events can decouple services by allowing components to publish facts without knowing their consumers, but this alone doesn't solve underlying architectural issues.
#4about 8 minutes
Differentiating event sourcing from event streaming
Event sourcing involves a component using its own past events to make future decisions, unlike event streaming where one component simply consumes another's events.
#5about 4 minutes
Introducing CQRS to solve event sourcing's limitations
CQRS separates the command model for handling changes from the query model for providing current state to address the limitations of pure event sourcing.
#6about 7 minutes
Moving from event-driven to message-driven thinking
A truly message-driven architecture requires discipline and uses distinct message types like commands, events, and queries for different communication intents.
#7about 12 minutes
Demo: Refactoring a monolith into microservices live
A live demonstration shows how an application built with location transparency can be refactored from a monolith into microservices by simply moving code between modules.
Related jobs
Jobs that call for the skills explored in this talk.
Matching moments
05:22 MIN
Adopting the Axon framework for true event sourcing
From event streaming to event sourcing 101
08:00 MIN
Q&A on DDD, shared models, and microservices
It’s all about the domain, honey ! Experiences from 15 years of Domain-Driven Design
00:46 MIN
Key takeaways on adopting event sourcing
From event streaming to event sourcing 101
05:21 MIN
Understanding event streaming versus event sourcing
From event streaming to event sourcing 101
05:40 MIN
Evolving from classic microservices to event-driven design
Kafka Streams Microservices
02:17 MIN
How to introduce new patterns like event sourcing
Seven Myths, Three Reasons, One Goal
00:47 MIN
Using command query responsibility segregation (CQRS) selectively
Architectures that we can use with .NET
05:20 MIN
How event sourcing provides a complete audit trail
Monoskope: Developer Self-Service Across Clusters
Featured Partners
Related Videos
27:33From event streaming to event sourcing 101
Gerard Klijs
46:24The Rise of Reactive Microservices
David Leitner
24:25Autonomous microservices with event-driven architecture
Florian Lenz
32:03Implementing an Event Sourcing strategy on Azure
Eldert Grootenboer & Olena Borzenko-Turianska
24:26Architectures that we can use with .NET
Alexej Sommer
25:05Microservices? Monoliths? An Annoying Discussion!
Eberhard Wolff
45:36What is a Message Queue and when and why would I use it?
Clemens Vasters
30:12Modulith Instead of Monolith - Pragmatically Towards Microservices
Hendrik Lösch
Related Articles
View all articles.gif?w=240&auto=compress,format)
From learning to earning
Jobs that call for the skills explored in this talk.
Speech Processing Solutions
Vienna, Austria
Intermediate
CSS
HTML
JavaScript
TypeScript
CONTIAMO GMBH
Berlin, Germany
Senior
Python
Docker
TypeScript
PostgreSQL
Amdocs
Kontich, Belgium
Senior
Terraform
Kubernetes
Machine Learning
Continuous Integration
CodeGuild
Amsterdam, Netherlands
€4-6K
Intermediate
gRPC
NoSQL
Docker
MongoDB
+1
CodeGuild
Utrecht, Netherlands
Remote
€4-5K
Intermediate
Docker
MongoDB
Node.js
+2
Agiliz