Skip to main content

Azure Blob Storage - More storage and throughput

One of the core services of Microsoft Azure is Azure Storage that is used to store binary content, key-values pair (Azure Tables)  or message queue (Azure Queues). In today's post, we will discover how a small change in Azure Storage capabilities is changing our life and simplify our IT solutions.

Current solutions
The current maximum capacity of Azure Blob Storage used to be 500TB. Even if this might sounds a lot, there are multiple cases when you had to overcome this limits. If you have a system where devices and users are uploading content to your system, than you can reach easily 2-5TB per day that would force you to use a new Azure Storage account every 3 months.
To overcome this limitation, your solution needs to be able to manage Azure Storage accounts automatically. Besides being able to clean and archive content automatically, you will need a system that can create a storage account on the fly and redirect traffic to it. When you use multiple Storage Account, you are forced to store not only information related to what content you are storing, but also a mapping related to was Storage Account  has the specific content.
Even if creating and managing a Storage Account is not complicated, it is adding an extra complexity on top of your current application. This can be translated in extra management costs and possible bugs (or even strange behaviors that are hard to reproduce).

Small things like this make our life a little more complicated and force us to add more complexity to our system.

Blob Storage Throughput Increase 
I was happy to find out that these days might be over. At least for applications that are using less than 5PB of blob storage.
Azure Team just announced that they increased the capacity of blob storage from 500TB to 5PB. This is a big step forward, allowing us to plan and design our systems more simple. At least most of the application will not need to use multiple storage accounts to increase their storage capability.
Of course, when you increase the storage capability you also need to increase the bandwidth speed together with the number of transactions that are allowed (TPS). This was also increased with at least 2.5 times.

Below you can find the thresholds that were increased:

  • Max capacity for Blob storage accounts - 5PB (10x increase)
  • Max TPS/IOPS for Blob storage accounts - 50K (2.5x increase) 
  • Max ingress for Blob storage accounts - 50Gbps (2.5-10x increase)
  • Max egress for Blob storage accounts - 50Gbps (2.5-5x increase)65

Remember that this new limits applies only for Azure Blob Storage. For the other services the old limits remains the same.

Final thoughts
The current trend is looking good and put Microsoft Azure in a good position. When this kind of updates occurs, it is more than increasing the threshold of a service. It is about charring on what customer needs.
Yes, we had workarounds for these limitations, but Microsoft is making our life much better by offering us what we need.




Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP