4 ms·
Does the managed service actually require that each user get their own container? For some applications, particularly collaborative ones, it would make much mor
by mwcampbell 5y ago
Does the managed service actually require that each user get their own container? For some applications, particularly collaborative ones, it would make much more sense to have a container for each top-level thing that the users are collaborating on, e.g. one per document. I think Sandstorm [1] got this right with its concept of grains, and I've long wanted a tool that brought that model, a stateful container per high-level object, running arbitrary code (unlike Cloudflare Durable Objects), to the world of hosted SaaS. Speaking of Cloudflare, I'm looking forward to seeing what their edge containers can do, when that feature is eventually made public.
[1]: https://sandstorm.io/ https://sandstorm.io/
- paulgb 5y ago> Does the managed service actually require that each user get their own container? For some applications, particularly collaborative ones, it would make much more sense to have a container for each top-level thing that the users are collaborating on, e.g. one per document. Exactly right. We do not actually require that every user gets their own container; that's a decision that's entirely up to your app. Our API spins up an instance and returns its hostname, and then you can connect to it from as many clients as you like.