Since every end user is running their own instance of your app, you never need to worry about scaling. You can pretend your app only runs on a single machine.
What about "big" users? Scaling is not just for multi-tenant systems.
Yes, that is a good point. Let's get this out of the way: not all apps fit into this model. If you as a single user have needs that require the power of more than one machine, Sandstorm might be the wrong platform for it.
But a lot of what users need from day to day fits quite well.
Also, Sandstorm does potentially have an answer for things that do really need multiple machines: you can have multiple instances of the app that talk to each other through Cap'n Proto RPC. But obviously, at that point, it's not so much simpler than the status quo.
Comments
What about "big" users? Scaling is not just for multi-tenant systems.
Yes, that is a good point. Let's get this out of the way: not all apps fit into this model. If you as a single user have needs that require the power of more than one machine, Sandstorm might be the wrong platform for it.
But a lot of what users need from day to day fits quite well.
Also, Sandstorm does potentially have an answer for things that do really need multiple machines: you can have multiple instances of the app that talk to each other through Cap'n Proto RPC. But obviously, at that point, it's not so much simpler than the status quo.
Servers get pretty big these days; like C1M big. If Scoble can't fit on a single server maybe he should be more judicious about his "friending".