7 ms·
There are all sorts of examples of this in the real world, because it's often not feasible to group everything you'd like into a single transaction. As a trivi
by foobazgt 3y ago
There are all sorts of examples of this in the real world, because it's often not feasible to group everything you'd like into a single transaction.
As a trivial example, consider any interaction with a third party. Once you're into that territory, you're talking logs, asynchronous retry queues, compensating operations, etc.
Sometimes the surface area of your company's product gets so large that, in order to scale, you interact with other teams as if they were 3rd parties.
- wg0 3y agoWe are not talking about third parties. Microservices are always first party, all that you own or some other team within your organisation owns even if they get deployed onto different clouds or something. Easier would be to admit that the microservices idea was the biggest fad in the history of computing and milked by consultancies to no end while compounding the complexity of software development to unprecedented levels, needlessly.