Do... or do not: Why Yoda doesn't use microservices

What this post added

This post elaborates on the challenges of state management in microservices, contrasting them with the transactional guarantees of ACID databases. It introduces the concept of a dedicated state management platform (like Temporal/Cadence) as a solution, highlighting its ability to provide durable execution and abstract away the complexities of distributed state management. The post emphasizes how this approach allows developers to benefit from microservices' agility without sacrificing reliability, drawing parallels to atomic database transactions and the 'do or do not' principle.