We're working on a load-balancing/DR architecture, and I'm trying to figure out the best way to implement it. Basically, we want to have "Origin-East" and "Origin-West", each with a health check. So far so simple. But here's where it gets more complicated.
- Is it possible to tell Fastly to send requests to the lowest-latency or geographically-nearest backend? Or is this something better handled at the DNS or routing levels? If we have to just do straight 50/50 that's OK, though.
- Each backend should really be a failover set itself, where for example requests would go to Origin-East-A unless it was unhealthy, and only then would requests go to Origin-East-B. If both East backends become unhealthy, then everything would start to go to the West backends.
Is this reasonable? Any suggestions on how best to implement this, or better ways to do things?
Please sign in to leave a comment.