2 ms·

I was thinking about Datomic when I read this, and yet came to exactly the opposite conclusion :) Datomic may be something like 'event sourcing' internally, bu

I was thinking about Datomic when I read this, and yet came to exactly the opposite conclusion :) Datomic may be something like 'event sourcing' internally, but it works so well because it abstracts and hides the naked overreach that the article pounds against. Datomic users think of it as a DB, not a stream of events. So I don't think that Datomic users are following the 'event sourcing' model.

vemv 8y ago
Fair point... but, events in the style of "User address changed" are very repetitive, wasteful, fragile etc. So stopping seeing user-address-change as (primarily) an event is a win. One always can fall back later to perceiving user-address-change as an event. For "real" events (e.g. "Transaction fraud detected") possibly I wouldn't use Datomic at all even if it was my primary DB. There are more suitable pub-sub systems. And that results in a neat separation of concerns: data changes in one store, actual business-valuable events in the other.