Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
I have set up Umbraco to serve media (and cached media e.g. image crops) from Azure Blob storage.
Is this enough? Or should I also use Azure CDN?
I can see how to set add CDN to my Azure storage, but I assume that some settings in Umbraco should also be configured. Can anyone share their insights?
Here is my summary from a discussion on this topic on Slack:
Unless you are serving numerous (or very large) files, the CDN is not really worth doing.
Just by using blob storage for media and cache (e.g. crops) you have managed to centralise the media (i.e. it is no longer held locally).
The webapp will be a constraining factor (as any request for /media/ is first handled there).
One argument for using a CDN is that it is more likely to support HTTP/2 - but that is well outside my current use case.
Isn't it possible to just have the front-end emit media links to https://site.blob.azure.com/media/ instead of https://site/media/ to mitigate this?
That's how a CDN endpoint against the BLOb Storage Container would have to work anyway, with links to https://cdn.site.azure.com/media/, right?
That sounds reasonable... but you probably want it to run through the webapp to generate any missing (previously unrequested) crops.
(I think that's how it works... I'm still a relative noob in the Umbracoverse.)
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.
Continue discussion
Azure Blob storage and Azure CDN
I have set up Umbraco to serve media (and cached media e.g. image crops) from Azure Blob storage.
Is this enough? Or should I also use Azure CDN?
I can see how to set add CDN to my Azure storage, but I assume that some settings in Umbraco should also be configured. Can anyone share their insights?
Here is my summary from a discussion on this topic on Slack:
Unless you are serving numerous (or very large) files, the CDN is not really worth doing.
Just by using blob storage for media and cache (e.g. crops) you have managed to centralise the media (i.e. it is no longer held locally).
The webapp will be a constraining factor (as any request for /media/ is first handled there).
One argument for using a CDN is that it is more likely to support HTTP/2 - but that is well outside my current use case.
Isn't it possible to just have the front-end emit media links to https://site.blob.azure.com/media/ instead of https://site/media/ to mitigate this?
That's how a CDN endpoint against the BLOb Storage Container would have to work anyway, with links to https://cdn.site.azure.com/media/, right?
That sounds reasonable... but you probably want it to run through the webapp to generate any missing (previously unrequested) crops.
(I think that's how it works... I'm still a relative noob in the Umbracoverse.)
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.