Greg Young - CQRS and Event Sourcing - Code on the Beach 2014

Channel:Code on the Beach · Length:1:03:48 · Published:2014-09-08 · Views:170129

Watch on YouTube

Summary

Greg Young's Code on the Beach 2014 talk on CQRS and event sourcing. He argues mature domains are built on facts that occurred rather than current state, and covers the business and technical benefits.

Why HN recommends it

HN developers recommend it as the talk that changed how they model systems, and as a clear intro to event sourcing's motivations.

forever changed how I think about modeling systems, preserving history — HN, 2022

Software architecture & design · Databases & storage

Subtitles (excerpt)

okay guys we're gonna get started okay so I want everyone to stand up really quick and now I know you can take directions so sit down Lizzie who don't know me my name is Greg young my day job is I design a database as in building the actual database engine I normally do not wear shorts and t-shirts around but we are on the beach so that's okay what we're going to talk about today is CQRS and event sourcing and this is actually a big problem just on the slide everyone always talks about CQRS and event sourcing when really it's event sourcing and CQRS when I first started teaching people about CQRS em event sourcing it was advantageous to teach them CQRS first and then teach them event sourcing you can use CQRS without event sourcing but with event sourcing you must use CQRS and we're talking about what both of those concepts are I've been talking about this subject for a very very long time in fact the first time I ever did talk about this was in 2006 at Q con San Francisco and actually some of the slides are still the same from all the way back then I have probably done this or a similar talk 50 times over the last couple years when I did the first talk is actually it was awful so I come

On Hacker News

Not about dev tools per se, but this talk by Greg Young on event sourcing & CQRS forever changed how I think about modeling systems, preserving history, and supporting multiple read models/versioning. Really clear walkthrough of the types of problems that benefit from an event sourced system, how event sourcing addresses them, and exploration of new use cases it enables. [VIDEO] — ssalka, 2022-06
The following talk about event sourcing (not listed in the article)•, really made an impact on me: Event Sourcing - Greg Young [VIDEO] •: Not that I really expected it to be I guess. — stock_toaster, 2016-12
For a fun introduction to this concept and the motivations behind it, you may watch Greg Young's talk [VIDEO] — rhizome31, 2019-02
I agree with you it's tough to sell CQRS, it's like trying to explain to someone that their business should use a database in one line. For me event-sourcing is a historical layer below your existing database that allows you to replay the sequence of events that got your database to its current state. If I had to businessify it, maybe it would be 'Wolkenkit is a framework that allows you to save … — matthewaveryusa, 2018-12
Greg Young also cautions "Do not tell me you've built an event sourced system"* (or something along those lines) meaning that you should be careful to apply the pattern only to the part(s) of the system that makes sense (due to the increased complexity of ES) * I think it's in this talk [VIDEO] — bottlenecked, 2017-09

Related videos