Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If you are considering event sourcing, run an event/audit log for a while and see if that does not get you most of the way there.

You get similar levels of historical insight, with the disadvantage that to replay things you might need to put a little CLI or script together to infer commands out of the audit log (which if you do a lot, you can make a little library to make building those one off tools quite simple - I've done that). But you avoid all the many well documented footguns that come from trying to run an event sourced system in a typical evolving business.



I've done this.

We have a customer whom we bill for feature X.

Does he actually have feature X or are we billing him for nothing?

With ES: We see his Subscriptions and Cancellations and know if he has feature X.

Without ES: We don't know if he subscribed or cancelled.

With audit log: We almost know whether he subscribed or cancelled.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: