Event Sourcing might be one of the single most idiotic ideas we've ever had as a specie, up there amongst the belief in that Heroin cures all pain, communism eliminates poverty, and lobotomy cures schizophrenia. Literally, it's "on pair" in stupidity with patents for "toilet paper dispensable hats" and "umbrellas for fish". Yet still, software developers are flocking to it like flies to bright lights ...
The problem with event sourcing is that it increases complexity by 3 orders of magnitudes. In addition it completely destroys performance, since now you've got to potentially retrieve 10,000+ records to understand "the current state" of an item in your database. On top of that, it makes it literally scientifically impossible to scale the system, because once you reach 1 million "changes" to an object, there's literally not enough RAM in the world to store the objects required to actually retrieve a single record. Then try to retrieve 20 records ... 😂
Seriously, somebody needs to say this out loud, and it might as well be me ...
Event Sourcing is never needed, and its only effect is that it complicates your architecture, destroys your ability to scale, and murders performance
At this point I'm expected to actually explain what event sourcing is, but for me, that would be an exercise equivalent to teaching how to murder people without getting caught - So I think I'll pass for obvious reasons. However, if somebody mentions "event sourcing" just throw them out the window. You can thank me later 😊
Top comments (0)