Greg Young - CQRS and Event Sourcing - Code on the Beach 2014
Code on the Beach4 HN recommenders · recommended in 4 months, 2016-2022
170K views · 12 years ago · talk · evergreen
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.
HN developers recommend it as the talk that changed how they model systems, and as a clear intro to event sourcing's motivations.
48:04Greg Young — A Decade of DDD, CQRS, Event Sourcing
Domain-Driven Design Europe
190K views • 10 years ago
54:25Event Sourcing • Greg Young • GOTO 2014
GOTO Conferences
102K views • 11 years ago
47:43"Turning the database inside out with Apache Samza" by Martin Kleppmann
Strange Loop Conference
205K views • 12 years ago
54:52Introduction to NoSQL • Martin Fowler • GOTO 2012
GOTO Conferences
1M views • 13 years ago
52:29"I See What You Mean" by Peter Alvaro
Strange Loop Conference
59K views • 11 years ago
1:06:24Rich Hickey: Deconstructing the Database
InfoQ
106K views • 14 years ago
35:33Visualising software architecture with the C4 model - Simon Brown, Agile on the Beach 2019
Agile on the Beach
553K views • 7 years ago
51:27Google I/O 2012 - Go Concurrency Patterns
Google for Developers
894K views • 14 years ago
42:31"Datafun: a functional query language" by Michael Arntzenius
Strange Loop Conference
9K views • 9 years ago
41:08"Transactions: myths, surprises and opportunities" by Martin Kleppmann
Strange Loop Conference
84K views • 11 years ago
51:40Domain Modeling Made Functional - Scott Wlaschin
NDC Conferences
71K views • 9 years ago
51:02An Introduction to SQLite
Google TechTalks
80K views • 19 years ago
43:39CRDTs and the Quest for Distributed Consistency
InfoQ
68K views • 8 years ago
50:06The Many Meanings of Event-Driven Architecture • Martin Fowler • GOTO 2017
GOTO Conferences
677K views • 9 years ago
40:42Lucas Cavalcanti & Edward Wible - Exploring four hidden superpowers of Datomic
ClojureTV
29K views • 11 years ago
59:13AWS re:Invent 2019: [REPEAT 1] Amazon DynamoDB deep dive: Advanced design patterns (DAT403-R1)
AWS Events
115K views • 6 years ago
43:04Corporate Open Source Anti-patterns
Bryan Cantrill
24K views • 12 years ago
54:58Keynote - JSON Graph: Reactive REST at Netflix
Association for Computing Machinery (ACM)
41K views • 11 years ago
22:29Gopherfest 2015 | Go Proverbs with Rob Pike
The Go Programming Language
317K views • 10 years ago
54:54Breakout Session Presented by Dan Robinson of Heap at PGConf Silicon Valley 2015
Citus Data
14K views • 10 years ago
5 comments from 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. ▶ this video
For a fun introduction to this concept and the motivations behind it, you may watch Greg Young's talk ▶ this video
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 and replay your entire business's history so you never miss a key insight again.' From a technical perspective, engineers can focus on the product and organically build and destroy the data structures around a changing business instead of trying to find the perfect data-structures that will inevitably be incorrect as the business grows and evolves. You get regression tests for free, and you get backups for free which may be nice-to-haves when the business is small, but absolute requirements once you have real customers paying real money. Not sure how I would squeeze that in an elevator pitch though. Greg Young's presentation on event-sourcing is pretty great, you may find some inspiration there: ▶ this video
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 ▶ this video
The following talk about event sourcing (not listed in the article)•, really made an impact on me: Event Sourcing - Greg Young ▶ this video •: Not that I really expected it to be I guess.