3 ms·
It's interesting, reading about how my counterpart at other shops do it. In our own Django web app, we basically just use the load balancer for deploys. Our se
by methodover 11y ago
It's interesting, reading about how my counterpart at other shops do it.
In our own Django web app, we basically just use the load balancer for deploys. Our service provider (Linode) has a nice API, so when deploying we just do one server at a time and direct traffic away from the ones doing the upgrade. It's not complicated and works just fine... At least when there are just two machines.
- joeyspn 11y ago+1 for rolling upgrades... Having 2+ appservers makes upgrades easier and increases resilience in general. Docker makes this really easy...
- cdnsteve 11y agoCould you provide more details on this?
- SEJeff 11y agoI do pretty much the exact same thing, but with Mesos[1], Aurora[2], and Aurproxy[3] (which is nginx). It sends traffic to a new instance only after the healthchecks are passing. Makes for a really nice rolling restart workflow. [1] http://mesos.apache.org/ http://mesos.apache.org/ [2] http://aurora.apache.org/ http://aurora.apache.org/ [3] https://github.com/tellapart/aurproxy https://github.com/tellapart/aurproxy