In my opinion the article does not put enough weight on lack of transactions in a microservices architecture. Of course you can add distributed transactions, but doing so makes the architecture much more intertwined and much less error-proof.
It's always fun diagnosing rarely occurring race conditions in a system with many services, work queues, some eventual consistent components, and various databases with their own transactions.
