3 ms·
> Whether that's the Oasis service, your own machines, or something in between. To clarify: does a "grain" just run in one place, or is each "grain" a cluster
by derefr 10y ago
> Whether that's the Oasis service, your own machines, or something in between.
To clarify: does a "grain" just run in one place, or is each "grain" a cluster of containers that can be spread-scheduled between disparate regions (i.e. "the Oasis service" and "your own machines" at the same time)? And, if the latter, do the cluster nodes have awareness of their locations, and can take advantage of that?
- yebyen 10y agoI have honestly no idea, other than I know that the grains are not permanent resident processes. IOW when they are not in use, they spin down and do not actively consume resources other than disk. I think the grain runs in one place, I think to use the container analog it would be one container, but as a point of clarification I believe that it is not using one of the container runtimes like docker or rkt that you will be familiar with, but uses its own sandboxing instead. I have not tried running the newly opened up Oasis backend so I can't really speak toward how it works. My experience with a single server running Sandstorm has been good, painless automatic upgrades, I would expect from what I know about this team, that since it's their dogfood they made it taste good.