/public

Google Canaries

There are some interesting release engineering and strategies in Google Cloud’s blog post How release canaries can save your bacon - CRE life lessons.

For example, on canary’ing web clients:

One solution is to version your JavaScript files (first release in a /v1/ directory, second in a /v2/ etc.). Then the rollout simply consists of changing the resource links in your root pages to reference the new (or old) versions.

… which is a great alternative to individually-hashed assets.