Cloud as a Story - Vunvulea Radu

Continuing the last post about Azure Web Apps and Data Disk size limit let's assume that you want to host inside a Web App a NuGet Server. The server would require more storage than you have available on the current tier that you use and upgrading the tier would be too expensive. The good part with NuGet is that we are talking about an open-source project that can be modified and extended depending on our needs and requirements. The current NuGet implementation allows us to store packages on disk or to fetch them from external data sources as long as they are available over HTTP. Basically, they are allowing us to have a remote repository  An interesting idea would be to extend NuGet to allow us to store package content inside Azure Blob Storage and not on the disk. This would involve the capability to fetch the payload of packages from Blob storage directly, without having to store them on a local disk. Taking into account the current implementation and how NuGet libr

This post is dedicated to Web Apps and how we should handle that case when we are out of disk space. Context When hosting our web applications as Web Apps inside App Service Plan we are limited to a specific number of GB that can be used by our web applications to store content. Depending on what kind of tier we are using we can have from a few GB of disk space up to 1TB of disk space. Inside an App Service Plan, we can host multiple Web Apps that are sharing the resources between each other, including the disk space. This means that if we have 4 Web Apps that are requiring 5GB of disk space each, at App Service Plan level we would require and consume 20 GB of disk space. Problem There are special cases when the disk storage space is not enough for our web apps. For example, there are cases when because of our business use cases we might need more data on disk that we have available inside the App Service Plans. Let's take a look at what are the options that we have at the

Number 7. This is the 7th year as Microsoft Azure MVP on Azure and cloud technologies. As usual, I'm happy and honored to be part of the MVP elite. Being close to the product teams and having the channels and mechanism to provide direct feedback to them it is one of the most important things that I can have. This year was a year with a lot of emotions because my renewal cycle used to be at the 1st of October. Starting from this year, our renewal cycle changed from October to July. The change was combined with a reduction of 21% of the MVPs at world-wide level. As you might already notify, I usually take a short break 2-3 weeks in June or July when I try to disconnect from technology. This time had passed, so let's see what the plans are for the next 12 months.         1. Local community events, at least once every 12 weeks         2. Weekly blog posts         3. Direct involvement in University programs         4. Create a functionality mapping and migration content b