3 ms·
> With microservices, you lose the ability to use database transactions across services/tables. Later on, when people realize this, it's too late. I don't foll
by rumanator 7y ago
> With microservices, you lose the ability to use database transactions across services/tables. Later on, when people realize this, it's too late.
I don't follow your reasoning. I mean, the ACID vs BASE problem you described is extensively covered in pretty much any microservices 101 course or even MOOC, along other basic microservices tradeoffs such as the distributed tax and ways to mitigate or eliminate these issues like going with bounded contexts. Why do you believe this is a mystery that no one is aware of?
- JamesBarney 7y agoI've seen a couple of projects where the original team didn't think they needed transactions, or underestimated how much harder eventually consistent distributed systems are to reason about than an acid system.