top | item 28704051

(no title)

diggs | 4 years ago

My first experience with event sourcing was having a new hire at a previous company try to shill it. It was a smaller company and he had previously built a career consulting on ES. Every problem we had he would come up with an argument for why ES would solve it. I soon learned he had zero technical ability, but was great at sounding credible to management. I liked to imagine him as a "seagull ES" practitioner. He flies in, sh*ts ES on everything, and flies out without having to deal with the mess.

Ironically I went on to use a lot of ES prinicpals in building a distributed deduplication engine for my previous startup after I left that company. We used a WAL which we were able to rebuild databases/projections from, ship to replica nodes for read replicas, push to S3 for resilient storage etc. it was an extremely powerful architecture for us. It was also complex and required a special skill set to work on and reason about.

I have to imagine anyone that advocates for "moving from CRUD to Event Sourcing" has recently been sucked into drinking the coolaid, and has no idea about the world of hurt they've signed up for, completely necessarily.

discuss

XeFVZZXLu45nfG|4 years ago

Similar thing happened on a project I joined. Except this person not only forced ES onto the business but their own specific library for it https://github.com/johnbywater/eventsourcing

The business eventually failed to due to this, due to slow implementation of simple features and many other issues with it.

I will never use ES due to this project, it's pointless, anything you can do with it, you can do without it.

jbywater|4 years ago

For the benefit for readers, of course I didn't force event sourcing on anybody.

The above allegation is utter bollocks, which apparently continues a stalking campaign by an ex-colleague who was forced to leave the company by the management.

This also happened FIVE YEARS ago, so the obsessiveness is disturbing.