You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to scale up for the Nov 2020 elections, we need to have the ability to do load balancing on heroku, as a tool in our pocket.
We are not looking for the perfect solution, just something what we can implement in the short term that works.
The head of the load balancer will need to be the cc.enciv.org domain, but we will need to test with another domain name before we switch over.
While we are doing load balancing, we will still need to support HTTPS.
Multiple undebate severs will spin up and connect to the same Mongo database URI. The proxy/redirect will distribute requests to the undebate servers in a round robin fashion (or whatever is simplest), without trying to figure out the load.
When a user visits a URL, would we proxy the request to the undebate server, or would we redirect? What's works, what's fastest to implement.
Would NGINX be a good choice.
The text was updated successfully, but these errors were encountered:
In order to scale up for the Nov 2020 elections, we need to have the ability to do load balancing on heroku, as a tool in our pocket.
We are not looking for the perfect solution, just something what we can implement in the short term that works.
The head of the load balancer will need to be the cc.enciv.org domain, but we will need to test with another domain name before we switch over.
While we are doing load balancing, we will still need to support HTTPS.
Multiple undebate severs will spin up and connect to the same Mongo database URI. The proxy/redirect will distribute requests to the undebate servers in a round robin fashion (or whatever is simplest), without trying to figure out the load.
When a user visits a URL, would we proxy the request to the undebate server, or would we redirect? What's works, what's fastest to implement.
Would NGINX be a good choice.
The text was updated successfully, but these errors were encountered: