3 ms·
As far as I understand, Kafka is positioning itself to be the leading Event Sourcing solution. I view event sourcing to be fundamentally different from message
by stolsvik 4y ago
As far as I understand, Kafka is positioning itself to be the leading Event Sourcing solution.
I view event sourcing to be fundamentally different from message passing. For a long time I tried to love event sourcing, but I see way to many problems with it. The primary problem I see is that you then end up with a massive source of events, which any service can subscribe to as they see fit. How is this different from having one gigantic spaghetti database? Also, event migrations over time.
RPC and messaging feels to me to be much clearer separated: I own the Accounts, and you own the Orders. We explicitly communicate when we need to.
I see benefits on both sides, but have firmly landed on not event sourcing.