fortunaTemporal

12 ms·

1.
An Emoji-based Guide for Speaking Distributed Systems and Temporal(temporal.io)
16 points by fortunaTemporal 3y ago|1 comments
2.
Video Live Coding Compensating Actions (Part of Saga Pattern) in Java(youtube.com)
6 points by fortunaTemporal 3y ago|0 comments
3.
by fortunaTemporal 3y ago
One pattern is having a Workflow that runs as long as the lifetime of a domain object and holds a conceptual lock on that object—it receives requests to modify the object, and makes sure to only perform one operation at a time. (like the st
4.
by fortunaTemporal 3y ago
Temporal has an event queue under the covers, so you don't have to implement (and debug) that yourself.
5.
by fortunaTemporal 3y ago
But in the scenario that the Saga pattern handles, you have at least TWO databases, and multiple processes can be modifying them in the meanwhile. It IS a gordian knot and you don't have a known clear place to restore from.
6.
by fortunaTemporal 3y ago
Here's the mind-blowing thing: Temporal handles those type 2 failures for you. So they are the footnote, and then the saga pattern can take up the whole article
7.
by fortunaTemporal 3y ago
Agree with what other commenters have said. Also wanted to say that with Temporal you can code Sagas in Go, Java, TypeScript, and PHP, and they're working on expanding to other languages as well.
8.
by fortunaTemporal 3y ago
Author of the article here. Yeah, @agumonkey I like that analogy a lot! Generally, that's a good way of thinking about it. The one additional bit of nuance is it's like a "safe" stack unwind while other processes could b