when does the complexity of event sourcing outweigh its benefits
Radmila Kovačević
·8022 views
So, I've been chewing on event sourcing lately. It sounds great for auditing, looking back in time, and keeping services separate. But honestly, I'm starting to worry about the extra work and how complicated it can get to set up and keep running. You've got to figure out how to change event schemas over time, manage the event log, and deal with the read models. When do you think just changing the current state directly is a better idea, even if you lose some of those event sourcing perks? I'd love to hear what you've actually done and why.
30 comments