3 ms·
Event Sourcing seems like the ultimate YAGNI architecture. You make an architecture that optimizes for future features at the expense of a coherent flow for th
by platz 8y ago
Event Sourcing seems like the ultimate YAGNI architecture.
You make an architecture that optimizes for future features at the expense of a coherent flow for the current features that you know you have.
it's like if you made pub-sub the core architecture for your system. very actor-system like, but also probably harder to understand the runtime behavior - control flow.
- hudo 8y agoTry to solve complex architectures that can handle race conditions without some kind of event sourcing, good luck with that
- pgwhalen 8y agoWith good tooling, it is arguably a lot easier to understand than a synchronous microservices architecture, because of the persistence of events. I’ll admit it’s probably harder to debug than a monolith, but that’s true of any distributed system.
- Fire-Dragon-DoL 8y agoIt's not like you are paying that price for long. Usually you'll start getting benefits the next month, as soon as someone wants new numbers in the dashboard. Or as soon as a new feature needs to be added