this post was submitted on 30 Jul 2026
9 points (100.0% liked)
Programming
27973 readers
273 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
One of the most complicated systems I worked on was based around event sourcing with a bunch if AWS DynamoDB tables and Kinesis streams. The original designers thought the inherent auditing capabilities and ability to generate view tables of anything would be a great for data durability and performance. In reality, nobody really understood how to effectively use it and ended up with events that were giant entity blobs so you couldn't understand changes, expensive AWS bills, numerous view tables that were impossible to know if they were in sync and correct, and difficult to evolve systems.
Event sourcing is a cool system, but friends don't let friends build systems they don't understand. There's a lot to event sourcing and I agree with the gist of this article of not modifying events. Though you can end up with a lot of events in a complex data model.