You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- use paths for versioning
- use major.minor.patch-commits_since_version_source
- remove purge instructions as it is no longer required
- add instruction to switch between versions
Pros
1. 100% atomic deployments. Content won’t be available till the big-bang
moment in which the origin’s path gets updated. Purge or content
expiration doesn’t affect what Azure CDN serves leaving you in full
control when new content starts being served.
2. better content organization and visualization
3. don't have to wait for cache to expire before Azure CDN begins to
serve a new version and it doesn’t require to execute a purge
action (cache invalidation)
4. enhanceed control over managing the content that Azure CDN serves
- it is possible to easily clean up the container enabling use cases
like history max level (e.g. keep last 3 most recent versions)
- it is just matter of target another container folder to rollback to
a previous version
- it allows SxS versions enabling more sophisticated use cases like
previewing new website versions before they are live and many other
scenarios (support older versions, variations, etc.)
Cons
1. if some content was being downloaded and newer version just kicked-in, user
might face some 404.
2. more space might be required, same content is now duplicated on every folder
solved: #114210
0 commit comments