Re:How release canaries can save your bacon
by gefh on Tuesday April 04, 2017 @03:48PM
(#14036516)
If one.js and two.js are really separate components, they should each get a version.
If they're closely coupled, they should be compiled together into one unit, to take advantage of deduplication, inlining, dead code elimination, fewer requests, better compression, etc etc.
[ Parent
| on HN ]
Re:How release canaries can save your bacon
by Touche on Tuesday April 04, 2017 @04:17PM
(#14036778)
Versioning assets separately by sticking them in new subfolders is just re-inventing ETags in a bad way. Just use ETags.
The point of the folder versioning scheme the article proposes is to make rollbacks easier. You can easily rollback a /assets/v2 folder to /assets/v1 by updating your server template, but if you have a dozen separate version folders (with different latest version numbers) for each resource then it's no longer easy to roll those all back.