News for hackers. Stuff that matters.

A comment on Mistakes we made adopting event sourcing and how we recovered.

Re:Mistakes we made adopting event sourcing and how we recov... by ilaksh on Monday July 01, 2019 @09:59PM (#20331486)
It seems like sometimes event sourcing is what happens when someone hears a requirement for audit logs and instead of just setting up the database audit logging system they decide to completely re-architect their entire system. So in the end it is more fun but often not necessary.
[ Parent | on HN ]
Re:Mistakes we made adopting event sourcing and how we recov... by stevesimmons on Tuesday July 02, 2019 @01:34AM (#20332406)
Event sourcing is most powerful when the data necessary to recompute the state is small but the amount of state you are potentially interested in subsequently accessing is large, most of which is computed.

It is also incredible useful for financial applications where risk models (credit risk, market risk, fraud, etc) need backtesting. If you can't read the time-ordering of state events directly, a Risk/Data Science team spends an inordinate amount of time reconstructing time histories of events inferred from a mix of static db tables, audit logs and periodic data warehouse snapshots.

[ Parent | on HN ]