the best pastebin that ever was or will be about pb HOT 4 OPEN

Application monitoring is kind of already addressed in the Nagios monitors issue we have open. Going to work on that on my next break probably.

stack high availability

We could set up a pair of haproxy instances, each in separate locations / with separate providers. Each instance can balance between two backends that share a DB. When we deploy new code we can do it to a pair at a time, test it, and then put it back in rotation. This gives us quite a bit of redundancy, and flexibility to break things without people noticing.

network uptime

I agree, Datacate has gone down several times. Between the two of us, we have access to two separate providers, I'm sure we can set something up that providers geographic redundancy and provider redundancy. Maybe have one balancer and its backends + DB on one provider, the second on another?

from pb.

HAProxy 1.5 looks pretty cool--even does IPv6, despite some people telling me otherwise.

However, we can do this for free with Varnish:

https://www.varnish-cache.org/docs/4.0/reference/vcl.html#backend-definition
https://www.varnish-cache.org/docs/4.0/reference/vcl.html#probes
https://www.varnish-cache.org/docs/4.0/reference/vmod_directors.generated.html

Examples: https://www.varnish-cache.org/docs/4.0/users-guide/vcl-backends.html#directors

Might as well make fewer stages in the request pipeline than more--I wouldn't be surprised if Varnish is faster anyway.

from pb.

Sounds good, fire

from pb.

A fair amount of this coversation ties in with @lericah's issue #101

from pb.