Greg Young — A Decade of DDD, CQRS, Event Sourcing

Channel:Domain-Driven Design Europe · Length:48:03 · Published:2016-04-11 · Views:190323

Watch on YouTube

Summary

Greg Young, who coined CQRS, looks back on a decade of domain-driven design, CQRS and event sourcing at DDD Europe 2016. He discusses where event sourcing applies and how simple its core can be.

Why HN recommends it

HN commenters cite it in event sourcing threads for Young's views on when to use it, including advice against cross-application event sourcing.

Greg Young reduces the "framework" to a function, a pattern match & a left fold. — HN, 2019

Software architecture & design · Databases & storage · Distributed systems

Subtitles (excerpt)

so what we're going to be talking about today is is really more of a retrospective over the last 10 years in dealing with event sourcing but we're not only going to be talking about event sourcing we're also going to talk a little bit about domain driven design so what we're gonna be going through I want to start off talking about the history of event sourcing and then we're going to look at some of the good things that have happened over the last decade then we're going to talk about some of the bad things that have happened over the last decade and the last thing we're going to talk about is things for the future areas where people haven't done a lot of research and a lot of focus on Event Source systems yet that at least I think are interesting now one thing I promise is we will not have these slides I have used these slides literally for like 9 years in explaining people event sourcing but if I go back and I look at the history of event sourcing it started off on clay tablets in Sumeria they use these clay tablets in order to track financials it's not a New Concept after suaria some things happened and then we came to 2006 this is not from qon 2006 they apparently have every single cuon archived

On Hacker News

See the presentation by Greg Young I linked to in another comment. One thing he talks about towards the end is the application for occasionally connected clients, which is one I'm looking to tackle myself in the next several months. ES may very well serve your needs, but I'd take a step back from the CRUD model and really think about the domain model. Something I do a lot of times when I'm lookin… — karmajunkie, 2016-10
I'm familiar with event sourcing. From what I understand, it's useful within bounded context/domain/app. I.e., from the outside you'd never know an app is event sourced (it's an implementation detail). Event sourcing is fantastic. My concern is with cross-app event sourcing: N copies of data/events across N apps. Greg Young strongly advises against this in this video: [VIDEO] I have no idea how t… — austinthecoder, 2026-01
It is worrying that a central figure to Event Sourcing & CQRS like Greg Young reduces the "framework" to a function, a pattern match & a left fold. Linked in the article [VIDEO] — fetbaffe, 2019-02
> Moving everything to be an event completely throws this out the window. This is either an antipattern or unrelated to event-sourcing depending on how you read it. "Event sourced" means that state within a transaction boundary is built ONLY through events which are regarded as persistent and immutable; evented is the term I'll use for state which is built when events happen, when those events ma… — karmajunkie, 2016-10

Related videos