This repository contains a proposal for a Stateful Serverless API specification.
This specification will need to be rewritten in a more official format. Its current form is temporary.
- Blog post + rendered specification
- Bikeshed specification (unrendered)
If you wish to participate, add your runtime here
The end goal is for this proposal to become part of W3C or WinterTC. If you are familiar with this process, please reach out on X or LinkedIn with next steps.
This repository is not intended to remain part of the rivet-gg org.
WinterTC is great specification for stateless serverless since migrating providers is as simple as updating a DNS record.
However, stateful serverless is significantly different since this spec is effectively defining a database, since ServerlessWorkers have persistent storage.
If the whole point of defining a common specification for stateful serverless is to encourage companies to adopt new technologies, then they'll also need assurances on their ability to migrate between providers. For example, Postgres provides the ability to use logical replication for live migrations and is used frequently.
The storage is the most rough section of this spec. It probably justifies its own spec.
SharedWorker connections cannot be interrupted. Can ServerlessWorker connections be interrupted? What happens if they are?