Can you have a single azure CDN instance configured for multiple items?
i.e I currently have a web role in a cloud service...the web role uses an azure storage account to store all images etc.
I currently have the azure CDN configured to the cloud service (prompted on create) - so now I have my various scripts and css etc on the CDN. I would like to also have all images/assets from the storage account on cdn too and was wondering if this could be done from this one CDN or would I need to create another CDN just for the images etc?
I'm not sure by what you meant by "same cdn" but you can use the same CDN profile to have two CDN endpoints. One pointing two the cloud service root. The other one to the images contents blob. Kindly find below two links that describe the two approaches both for the cloud service and the storage below.
Hope this helps!
Storage: https://azure.microsoft.com/en-us/documentation/articles/cdn-create-a-storage-account-with-cdn/
Cloud Services: https://azure.microsoft.com/en-us/documentation/articles/cdn-cloud-service-with-cdn/
Related
I have a website where I would like to cache the few images/stylesheets/javascript-files I have. Is it possible to have Azure CDN point directly on the files on my server, and then cache them, instead of having to upload them to an Azure storage?
It's not possible. Azure will not allow you to configure arbitrary domain as origin domain to support origin content pull. The only available targets are existing azure website, cloudservice or storage account.
Let us discuss your desired end goal.
If you want to improve your caching with CDN related functionality with the same domain name, take a look at Cloud Flare.
However, if you were going to a separate your content into a CDN domain and the application domain, you could look at expanding the following MSDN sample. The idea with this sample is so that as a deployment step, you upload all the CDN related content to the Azure Storage Account.
https://code.msdn.microsoft.com/windowsazure/Synchronizing-Files-to-a14ecf57
I have been exploring the features available in Azure and AWS. The fact that most features is not available or not clear.In CDN part i have comparisson criteria like 'Whether I can push/upload content to CDN Servers like in AKamai.
I have seen the feedback program and find that Custom-Origin is not available(
Link : http://feedback.azure.com/forums/169397-cdn/status/191761 ).But this one i could not find any link.Anyone has any idea?
No. Azure CDN currently does not support direct interaction (i.e. direct content upload, explicit or on-demand content expiration, etc.). It works as advertised serves files from Azure Storage Account or azure Cloud Service.
I'm creating a website where users will be able to upload various images when creating a new page on my website. What service does Microsoft offer to host many user uploaded images. Would a Blob suffice? If so, if I were to add a CDN, would it be worthwhile? From what I understand, a CDN copies the images on various servers. If my local server has 1 million images, would that mean all the other locations will have 1 million images as well? Would that be very costly?
Blob storage is the perfect place for images in Azure.
CDN is great for when your images are at least somewhat static and will be viewed more than once.
With CDN you do not pay for storage costs (on the CDN), but instead for transfers out of the CDN - http://azure.microsoft.com/en-us/pricing/details/cdn/
I should also mention that if you're using Azure and Blob storage is your primary facility for storing images, Azure's CDN does not have to be your primary CDN - and any CDN will work. CDN's are pretty commodity service these days.
HTH
A CDN on top of Azure storage would be useful if you have lot of users fetching the same file(hot files/Cache hits) Accessing files that are not heavily used will result in a Cache Miss. The CDN will then fetch the file from the origin (Azure Storage) before delivering it to the user. For such a scenario adding a CDN on top of Azure storage provides very little benefit.
We are migrating our PHP website to Azure Cloud Web Service (Web Role).
Currently the website saves user submitted image files to the filesystem via drive letter access. These images are then served via a url e.g. content.example.com.
What options have I got id I want persistent file storage on an Azure Cloud Web Service.
I am currently assessing BLOB Storage for this.
Thanks
Blob storage is the right answer. Although you could convert your images in base64 and save them in Azure Sql as well, it is really not recommended.
Check: Azure, best way to store and deploy static content (e.g. images/css)? or Where to store things like user pictures using Azure? Blob Storage?
One of the options to reduce re-writing of your application is to mount blob-storage as a network drive. Here is some information how to do it: http://blogs.msdn.com/b/windowsazurestorage/archive/2014/05/12/introducing-microsoft-azure-file-service.aspx
Mounting of the drives can be done on Web-Role start-up task and can be scripted.
I'm trying to find the best setup for my website on Windows Azure.
I have a front-end and a back-end website made in ASP.NET MVC4.
Both websites must use a shared same images. Font-end for displaying, back-end for CRUD actions. The image files are stored in a folder in the front-end web application and the url's to those images are stored in a mysql database.
Currenty i have 2 Windows Azure websites, but i can't access the images from the back-end website because there are stored in a folder on the front-end application?
What's the best setup and cheapest for this type of application?
2 websites with shared BLOB storage ?
A cloud service containing 2 webroles (front- and back-end) ?
... ?
Thanks
First you should not use web application's folder beside temporary operations. Since Azure means multi-computer environment, resource (image) won't be available for requester if you use more than one instance (machine)
I would go on 2 blob container. (not 2 blob storage account)
We do not have IP based restriction on blobs yet so as long as you don't share those addresses you will be fine. If you really need to have restriction you can use Shared Access Policy which you can find more details on Use a Stored Access Policy also you should review this one too Restrict Access to Containers and Blobs
I think that using a shared blob storage account is the right direction.
Using a local folder is not a good idea - on web sites and cloud services these are not persistent and you may lose your files. Either way - this is not a scalable solutions - if you'll add additional instances in the future you will not have access to the files.
Using blob storage will give you a location that is accessible from both locations and indeed from the client's browser directly.
You do not specify whether the images need to be accessed securely from the front end or not, if not that blob storage is particularly useful as they can be served from a public container on azure storage directly.