Scaling a Meteor Cluster

Let's try to scale a Meteor app using our new meteorhacks:cluster package. No need to use nginx or haproxy for load balancing and scaling.

Transcript

1. Scaling Meteor @meteorhacks with meteorhacks:cluster
2. This is how Kadira UI stated meteor instance (107.172.78.11)
3. Then we wanted to add more instances meteor instance (107.172.78.11) meteor instance (107.172.78.12) HaProxy (107.172.78.1)
4. Then we had an issue with HaProxy meteor instance (107.172.78.11) meteor instance (107.172.78.12) HaProxy (107.172.78.1) HaProxy (107.172.78.2)
5. Issues It’s a complex setup We are not really good at HaProxy debugging Adding new an instance is not easy
6. What if we could use only Meteor Instances?
7. Using meteorhacks:cluster meteor instance (107.172.78.11) meteor instance meteor instance
8. What if we could use every instance is a load balancer
9. With balancers meteor meteor meteor meteor meteor meteor
10. Benefits No single point of failure Distribute the DDP Traffic between all instance Everyone is a master
11. give me bulletproofmeteor.com here’s the initial HTML give me /sockjs/info PhantomJS How Meteor Works Here’s the sockjs configurations create the WebSocket Connections
12. Demo: BulletProof Meteor
13. Meteor Up Config
14. Meteor Up Config
15. Demo: BulletProof Meteor
16. Benefits No need to install additional tools No configurations (built for Meteor) Automatic node discovery Every instance is a load balancer
17. Benefits Works with any hosting provider by default can be used for A/B testing extend load balancing logic great for Mircoservices
18. Compared with Haproxy/Nginx They are proven and battle-tested Automatic discovery
19. Future more load balancing algorithms more stability and tests load balance direct websocket connections discovery backend from Kadira
20. github.com/meteorhacks/cluster