Event Sourcing • Greg Young • GOTO 2014

Channel:GOTO Conferences · Length:54:24 · Published:2014-11-13 · Views:102485

Watch on YouTube

Summary

Greg Young, who coined CQRS, gives an in-depth GOTO 2014 talk on what event sourcing is, when it is valuable and when it is not, along with its trade-offs and common misconceptions.

Why HN recommends it

HN commenters list it among the best introductions to event sourcing and use it to illustrate storing read-only events instead of mutating state.

Here's a youtube video about the benefits and attributes of event-sourcing. — HN, 2017

Software architecture & design · Databases & storage

Subtitles (excerpt)

it really was weird for me when I went to Copenhagen and they had it in the bleeding edge track so the first time I actually talked about event sourcing was at cuon 2007 um Martin was actually at this talk and I was scared senseless so I'm coming and talking about new ideas around domain driven design um messaging and these kinds of ideas and my front row was Martin Eric Evans and Gregor h I think I probably had about 30 glasses of coffee before I started and I went through my entire talk in like 17 minutes it was a really awful talk uh to be fair I think Martin gave me a red card Eric even told me it was a bad talk which if you've never met Eric he doesn't really say bad things but it's it's not new ideas and even going back as far as like 2006 2007 these ideas go way back way past that what really brought us towards looking at event sourcing was that we needed to have a log and we need to have a proper audit now for some systems this is very very important for other systems it's not so important that's what led us towards the idea of event sourcing and I've actually used a slide now since 2007 because the slide is so perfect what's interesting for me when we talk about event sourcing is that if you look at mature businesses and when I say mature I do

On Hacker News

It depends on what your goals are... I haven't read 'Practice and Principles', but I assume it focuses mostly on the OOP programming paradigm. I'd explore the functional programming paradigm. I say paradigm because it's possible to implement the functional paradigm in a traditionally imperative/OOP language like C++. (And it's possible to implement OOP/imperative paradigm in traditionally functio… — Leftium, 2023-02
There are forms of state that are reversible: essentially, you store read-only events instead of writing to existing state. The main disadvantages are more complexity and performance issues. Examples: - Event sourcing: [VIDEO] - CRDT - At the DB layer: [LINK] - You can also do it at the code level (but this is more like keeping copies of the old state): [LINK] — Leftium, 2026-01
I think your specific question can be answered by this video. It explains how all branching was removed by refactoring an imperative-style function into functional-style. The original code is on the top, the refactored code is on the bottom: [LINK] Besides being shorter and easier to reason about, functional-style can be easier to test because there are fewer logical paths to test (statement/cond… — Leftium, 2024-03
Learning Functional Programming can provide immediate benefits. However, FP practitioners tend to be bad at teaching/explaining (to non-mathematicians) and even worse at marketing[0]. I've attached a list of good resources on FP at the end of this comment. I also wrote an article on the benefits of functional programming: [LINK] Functional programming is more of a spectrum; not an "all or nothing… — Leftium, 2024-03
> But if someone can explain the problem better, I'm all ears. Assuming you mean it... Here's a youtube video about the benefits and attributes of event-sourcing. [VIDEO] Though the demo project is presented in the browser, I'm trying to demonstrate that I can model the game of Tic-Tac-Toe using a much smaller and comprehensible (I hope) graph. Additionally - because these are mathematical graphs… — orksliver, 2017-03

Related videos