Our time travel debugger at undo.io also uses a similar approach. But the world is different for time travel debug, in that you can replay the whole history of

Our time travel debugger at undo.io also uses a similar approach. But the world is different for time travel debug, in that you can replay the whole history of the recorded execution (my understanding is that this is not required for Durable Execution) but you cannot resume the real process. In fact, since it's used for capturing faults, you wouldn't generally want to resume execution - it's going to fail the same way (whereas a higher level restart framework might allow you to throw away some bad state and continue the computation - at the cost of not being able to precisely duplicate the bug).