Windows Azure Website Disk Space

Question

I have a website running windows azure in shared mode, and I am quite satisfied with it. But then I noticed that I only have 1 GB of free disk space, which is not enough. So I wanted to increase the size, but found out that there are two options that are both not good:

1) Acceleration to backup mode gives 10 GB, but for all websites that will work there, what? The cheapest hosting options provide more disk space for a single website. In addition, it does not make sense to me, since I am quite pleased with the speed of the general modus.

2) Using blob memory. So do I need to rewrite my code to post the azure? Is that not so? For me, one of the most important reasons for choosing azure over traditional web hosting was the promise of easy scaling, but my first moment of scaling, and this cannot be done easily.

I missed something, is there a better way to get more disk space for an azure Windows site?

Answer 1

To definitely use blob storage, the actual azure web servers should not be used for storage. Using blob memory will allow for better scaling.

Laser web servers are designed to handle volatile versions. They are designed to host only your application / service and give you the flexibility to easily create and destroy their instances. Given this flexibility, if you actually store things, you run the risk of losing this information when scaling down and around.

Then there is another case where you had two web servers with azure letters ... request number 1 goes to server # 1 and uploads the file. This, obviously, will be stored on the hard disk of servers No. 1. Now, if the same # 1 user returns a second time (or any user, for that matter), but this time balances the load on server # 2 and asks for this file - how does server # 2 know where to get this file?

In principle, saving files to the web server’s hard drive poses a scalability problem. To work around this problem, you must save all your files in a central location ... where the Azure Blob storage is used.

Azure was not designed as a magical unicorn that you just drop your application at, and it magically scales ... you need to change the mindset a bit from a single-server application to an application that can run on multiple servers around the world that require the same data from centralized location.