The article lacks an example demonstrating how it can solve a real problem. I felt the authors aren't able to come up with such a concrete example nor does it talk about its overhead and global state atomicity.
The goal of this article was to lay the concepts and give insight into the technical machinery, so you’re right, it didn’t contain a lot of concrete examples.
We've had enough of traditional orchestration frameworks. That's why we created dispatch.run, aiming to streamline coding by integrating resilience more naturally.
The core of our solution? Distributed Coroutines. These aren't your typical tools; they're designed to enhance flexibility and reduce complexity in distributed systems.
We've detailed our approach and the potential of Distributed Coroutines in a new blog post. It's about making development smoother and more intuitive.
Let's discuss the future of distributed computing.