And yes, Restate does not have any external dependencies. It comes as a single self-contained binary that you can easily deploy and operate wherever you are used to run your code.
Nice thanks. The ability to use cloud functions/lambdas is certainly intriguing and something I'd hoped would be possible with temporal when I first discovered it.
In a multi-replica / horizontally scaled setup:
- Does each replica get its own independent storage volume?
- How much state is replicated between each volume if so?
- What does a typical workloads journal look like in terms of storage size? How often does this get compacted / is there archival to cold storage?
- How do you manage upgrades to restate in the case of a change to the on-disk format? (Or is this designed to be static between releases)
The fact that it's without external dependencies also makes me wonder if it would be encouraged to have multiple independent deployments of restate managing different independent services/workflows to avoid noisy neighbors and single points of failure - seems like it might be lightweight enough that this is practical?
I'm particularly interested in the scaling characteristics, and how your approach to durable storage (seems no external database is required?) differs