←back to thread

31 points mxschumacher | 3 comments | | HN request time: 0.001s | source
Show context
reval ◴[] No.43700569[source]
Are there any self-hosted offerings similar to Durable Ojects? I like the idea of abstracting synchronization like this but enjoy being cloud agnostic.
replies(3): >>43702095 #>>43705000 #>>43714204 #
1. solardev ◴[] No.43702095[source]
Maybe a Valkey cluster for simpler use cases? Although that's more like Workers KV than DO.
replies(1): >>43703875 #
2. reval ◴[] No.43703875[source]
I wonder if temporal [1] could be used to create DO. Had anyone here tried it?

[1] - https://temporal.io/

replies(1): >>43707367 #
3. mlnj ◴[] No.43707367[source]
Although I have not used it as DO, I have been using it for durable workflows for a few years. The cached results of the workflow activities could give the feeling but the latency to read and write would be a dealbreaker for many. There is a lot of overhead in writing the interface between application code and Temporal workflow (for example, you can have conflicting object IDs that can be configured).

Self hosting Temporal with a Postgres datastore is usually how I deploy it and it works great, but at that point I'd just write it to a Valkey store if I just wanted a easy DO interface.