The Reactive Monolith – How to Move from CRUD to Event Sourcing
1–10 of 112 posts
Re: The Reactive Monolith – How to Move from CRUD to Event Sourcing
#2There is a typo on the reference part:
``` Martin Fawler, 2005 https://martinfowler.com/eaaDev/EventSourcing.html> ```
Fawler -> Fowler
Re: The Reactive Monolith – How to Move from CRUD to Event Sourcing
#3And then you realize that the CRUD db you moved away from operates on event sourcing (WAL) anyway. And thus you’re just doing inner platform effect.
Re: The Reactive Monolith – How to Move from CRUD to Event Sourcing
#4I feel bad for anyone who got sucked into event sourcing for general purpose applications. Like... I'm burning a candle for you right now.
The event stream stuff makes sense in some specialized use cases (LMAX?) but for general purpose stuff? Oof, no.
EDIT: Also, don't hate me folks, but any article that references Fowler should be looked at with just a little bit of suspicion. Not hating the guy but he's blown quite a bit of hot air in his time.
Re: The Reactive Monolith – How to Move from CRUD to Event Sourcing
#5This article doesn’t really explain event sourcing and some of the trade offs with event driven architecture in general (additional complexity).
I’ve heard Git is an example of event sourcing. It has all the info for you to be able to determine the current state from scratch if you needed to. I’m not sure why you’d see event sourcing as the next stage of evolution for a CRUD system.
Re: The Reactive Monolith – How to Move from CRUD to Event Sourcing
#6I feel bad for anyone who got sucked into event sourcing for general purpose applications. Like... I'm burning a candle for you right now. The event stream stuff makes sense in some specialized use cases (LMAX?) but for general purpose stuff? Oof, no. EDIT: Also, don't hate me folks, but any article that references Fowler should be looked at with just a little bit of suspicion. Not hating the guy but he's blown quite…
What makes event sourcing poor for general purpose stuff?
Re: The Reactive Monolith – How to Move from CRUD to Event Sourcing
#7I feel bad for anyone who got sucked into event sourcing for general purpose applications. Like... I'm burning a candle for you right now. The event stream stuff makes sense in some specialized use cases (LMAX?) but for general purpose stuff? Oof, no. EDIT: Also, don't hate me folks, but any article that references Fowler should be looked at with just a little bit of suspicion. Not hating the guy but he's blown quite…
What makes event sourcing poor for general purpose stuff?
Not OP, but the number of variants in the events makes the cardinality of the state of the system extremely large. Probably too large to be able to reason about fully. It makes weird bugs in the event schema likely impossible to debug should they occur.
Re: The Reactive Monolith – How to Move from CRUD to Event Sourcing
#8Earlier quoted context omitted.
What makes event sourcing poor for general purpose stuff?
Not OP, but the number of variants in the events makes the cardinality of the state of the system extremely large. Probably too large to be able to reason about fully. It makes weird bugs in the event schema likely impossible to debug should they occur.
This is exactly why 2-way data binding fell out of favor in modern UI development. Describing the problem as "the cardinality of the state of the system extremely large" is a succinct way of putting it. The non-linear increase in possible state quickly makes testing an uphill battle. And it's over when you can't have a comprehensive testing strategy, forget about it.
Re: The Reactive Monolith – How to Move from CRUD to Event Sourcing
#9https://codeopinion.com/event-sourcing-example-explained-in-...
Derek Comartin does a great job explaining event sourcing on his site. I really like him for being able to easily explain fairly technical ideas like this.
However, like others have said, this should be a tool reserved strategically for ideal situations, not a jackhammer for every task.
Re: The Reactive Monolith – How to Move from CRUD to Event Sourcing
#10From the same consultants that sold your VP on agile comes event driven architecture. Because your data model wasn't complicated enough already.