3 ms·
The saved coroutine state is an implicitly-defined data structure and they don’t support any kind of migration when the code changes, so the durability will be
by skybrian 3y ago
The saved coroutine state is an implicitly-defined data structure and they don’t support any kind of migration when the code changes, so the durability will be quite limited.
- achille-roussel 3y agoYou’re correct that code migration is still a to do, we’ll be exploring how to do that in the future. As you can imagine there are a lot of challenges with it, but ideas are welcome!
- skybrian 3y agoIt seems like generating some data structure definitions (similar to a protobuf) and checking them in along with the code would be useful? Then the compiler can tell you when they still match, or you made an incompatible change to the code. This seems like a situation where defining the data structure in two different ways might be good?
- dlock17 3y agoThis seems like a good use case for Cap'n Proto.
- chris6f 3y agoWe have a solution already, and we're exploring a few more. The durable coroutine library is one part of a larger system we're releasing soon. See https://stealthrocket.tech/blog/fairy-tales-of-workflow-orchestration https://stealthrocket.tech/blog/fairy-tales-of-workflow-orch... for more information :)