3 ms·

It supports too many apps/frameworks - It's too ambitious and not focused enough. Also, not all apps are the same when it comes to scalability - That's a false

It supports too many apps/frameworks - It's too ambitious and not focused enough. Also, not all apps are the same when it comes to scalability - That's a false assumption which pretty much of all PaaS providers make. There is more to scaling an app than just adding more machines - Services need to be scaled independently of each other based on usage; also, some services should run on their own dedicated hosts, some services require persistent storage also there are needs to be rules to define how services can talk to each other, recover from failures, etc... Developers NEED some way to specify HOW their services should scale - It can't just be fully 'automatic' - That's not flexible enough. If you look at typical Kubernetes config files, they are quite long/complex; this is because there are a LOT of factors/variables involved when it comes to running services inside distributed containers and you can't just abstract away from those details without seriously compromising flexibility.

kentonv 10y ago
Sandstorm is not a PaaS and is not intended to be an alternative to Kubernetes. It is not designed for running SaaS services intended to scale to millions of users. It is designed for running personal or internal employee-facing services, where there are anywhere between 1 up to maybe 10,000 users. The kind of scaling you describe simply isn't an issue in this domain. Moreover, Sandstorm takes a completely different approach to scalability called fine-grained containerization. The problems and solutions are really completely different from a Kubernetes-like approach. Read about it here: https://sandstorm.io/how-it-works https://sandstorm.io/how-it-works
- Taek 10y ago
  Sandstorm is exciting to me for personal reasons. Scalability is not an issue there, because all my apps already need to run on only one computer. Security and encryption is really important to me. Synchronization as well. Very excited about sandstorm because it seems to fix a lot of the gaps in my current flow.

kentonv 10y ago

Sandstorm is not a PaaS and is not intended to be an alternative to Kubernetes. It is not designed for running SaaS services intended to scale to millions of users. It is designed for running personal or internal employee-facing services, where there are anywhere between 1 up to maybe 10,000 users. The kind of scaling you describe simply isn't an issue in this domain. Moreover, Sandstorm takes a completely different approach to scalability called fine-grained containerization. The problems and solutions are really completely different from a Kubernetes-like approach. Read about it here: https://sandstorm.io/how-it-works https://sandstorm.io/how-it-works

Taek 10y ago
Sandstorm is exciting to me for personal reasons. Scalability is not an issue there, because all my apps already need to run on only one computer. Security and encryption is really important to me. Synchronization as well. Very excited about sandstorm because it seems to fix a lot of the gaps in my current flow.