Re:Meteor hits 1.0
by thathonkey on Tuesday October 28, 2014 @03:28PM
(#8523023)
The "running from a single box" at the end seems like it could be the most important part of the equation. Would you agree? Or rather, would that be the recommended place to start optimizing if your app runs into scaling problems?
Here is a very fine blog posts series on scaling Meteor horizontally, please consider looking at it: https://meteorhacks.com/pro-meteor/
Re:Meteor hits 1.0
by thathonkey on Tuesday October 28, 2014 @05:51PM
(#8523818)
Interesting, thanks. In that first blog post it mentions that Meteor serves static files. Is that a requirement?
edit: posted too soon they talk about it here https://meteorhacks.com/does-meteor-scale.html
And you can use cloudflare or some other CDN very easily. See: https://meteorhacks.com/cloudflare-meets-meteor.html
No, it is not a requirement. Meteor also supports serving static files from a CDN.
Re:Meteor hits 1.0
by swartkrans on Tuesday October 28, 2014 @04:00PM
(#8523212)
I don't know how you could load balance meteor easily, but you could put your mongodb instance anywhere and pass in its location to meteor. This doubles your risk for downtime because of hardware failure though, your uptime is no longer as good as a system that depends on the uptime of a single machine.
Scaling low-latency data synchronization is a challenge for scalability for sure! We are gradually building better and better drivers with persistence to MongoDB.
The scalability can vary greatly depending on your application's data schema, usage patterns and amount of writes.
If you watch the mentioned talk carefully, the speaker describes a collaboration tool with log replay with a lot of actions and running from a single box.