8 ms·
Ya, I should probably: show by example, not dismiss Event Sourcing so readily, not get sucked into a No True Scotsman argument, or all the above. Fowler's high
by specialist 7y ago
Ya, I should probably: show by example, not dismiss Event Sourcing so readily, not get sucked into a No True Scotsman argument, or all the above.
Fowler's high level overview is https://martinfowler.com/eaaDev/EventSourcing.html https://martinfowler.com/eaaDev/EventSourcing.html
Which doesn't cover the persistence, the actual data model. In particular, I disagree with the notion of a separate Audit Log.
More recently, on recent projects, anyone using a message queue or bus has called their goo Event Sourcing. Which is mostly just shuttling around analytics. Not modeling organizational behavior as events. Not considering how to design the event sinks (RDMBS tables).
Someday I'll write up what I did for healthcare records. Sorry I haven't already.