Currently I host my Meteor App on one docker + another docker for MongoDB on DigitalOcean Droplet 2 Gb RAM. I used NGINX to manage my web apps (4 web app running on Docker).
I planned to use load balancer to load balancing one of my web app. I see that I can use NgInx or Meteor Up for load balancing of my web app.
If you mean with mup that you have to use meteor-cluster I’ve to say that this is a bad idea. I’ve used it in a chat application and the whole server crashed very often (I’ve added 3 VPS systems). There is a issue open about it, @arunoda seems to have no time to maintain it anymore if you see how many issues are still opened.
I thing using NGINX as a load balancer is a common setup, but you have to configure it right, f.e. activate STICKY_SESSIONS or IP_FORWARDING, otherwise your application wouldn’t work properly.
We use NgInx for load balancing between our 2 droplets. It seems to work fine.
We have one Digital Ocean’s Droplet with 4 CPU and 8 Gb RAM for 1 NgInx, 2 keystone App, 2 TelescopeJS Apps, 1 Odoo ERP, 1 postgresql. All are running in their own docker containers.
We have one Digital Ocean’s Droplet with 2 CPU and 4 Gb RAM for our MongoDB Server with 4 oplog. Each run on their own Docker container.
Thank you so much! What’s the difference between what I see other people saying to do and what you did regarding hash? I see in many places people just write:
If, however, the majority of the traffic to your site is coming from clients on the same /24 network, IP Hash doesn’t make sense because it maps all clients to the same server. In that case (or if you want to hash on all four octets for another reason), instead use the Hash method with the $remote_addr variable.
ip_hash only looks at the first three octets of the address. Say for instance a large corporation or university accesses your site. They will all be on the same instance. With remote_addr, they can get spread around more.