"Canary" logic at Fastly?
I'm wondering if it's possible to do a kind of canary deployment of Fastly configuration itself. That is, I want to roll out a new configuration version, but only have x% of traffic go to that new configuration. The only way I've been able to think of doing it is with multiple services, set up like
- www.example.com - the visible front end; has no real configuration other than logic to split traffic between origins, which are
- www-main.example.com - the main branch
- www-canary.example.com - the canary branch
Is there any other way to achieve canary deployments of Fastly configurations? The only docs I've been able to find talk about using Fastly to split traffic between two versions of some other service used as an origin.
Please sign in to leave a comment.