Discussion about this post

User's avatar
Am I red yet's avatar

Quick and easy to follow introduction to sagas, thank you very much 👍

Expand full comment
Saurabh Dashora's avatar

Great explanation Raul.

I especially liked the point about observability being a key player while implementing Sagas. Without that, it can become really difficult to make sense of things when they go wrong in a Saga flow. We realized that pain in one project a few years back, where multiple teams ended up blaming each other without any clear indication of which service was causing a particular issue.

Orchestration makes this somewhat easier as you mentioned, but again it's better to use that mainly if all services are within the team and you don't have to ping 5 people to understand what's happening...lol.

Expand full comment
2 more comments...

No posts