Reviews (1-5 of 5)
- It has allowed us to add content to the cloud that everybody globally can use. This makes it so much easier for us to maintain version control. Everybody is linking to the same version. And we have control of what revisions are uploaded to replace the one already there.
- By moving these large digital files out of our server room and onto the cloud, we have reduced the pipeline needs for our IT servers on-site.
- One thing we wish was done better is more guidance for building it out from day one. We did not know what we were doing and until we hired an implementation person that understood what we wanted to do. We spent a lot of time and money doing things over several times.
- Help customers hook up with talented (local) implementation specialists would be great.
Azure Blob storage is currently used in various ways at our company.
First, like cloud storage for various Azure SaaS platforms. Things like managed SQL instances and data lake storage for Azure AI / ML. It is useful in that it is tiered, so you can use hot tier for these use cases.
Secondly, a more common use is to use the cold and archive tiers as a cheap location to store long-term backups and archives. We think of it as a replacement for tape offloading in our DR strategy. One thing to be away from is that the cost to bring those backups/archives back from the cloud can be very high. So this is used more as a place of last resort for disaster recovery currently, but it definitely has its place.
- Tiering - Hot/Cold/Archive.
- It allows you to pay for the performance you need for the task at hand.
- Easily consumed and accessed.
- Expensive to egress your data, especially in a true DR scenario from cold or archive tier.
Well suited for newly developed micro applications that need to access data in the cloud.
Well suited for being the storage layer for SaaS offerings within the Azure Service Catalog. The integration is usually built-in.
Well suited for backup storage target for long-term RPO objectives, when the expectation of actual retrieval need is very low.
Well suited for long-term offsite archival storage.
Well suited for emergency storage needs (burst storage) for an immediate need.
Not appropriate for data that has high amounts of ingress and egress churn.
Not appropriate for applications that require ultra-low latency response time from the storage layer.
- Reduced cost. We were able to reduce our storage infrastructure by several hundred terabytes by consolidating redundant copies and dedupe/compression on files.
- Extremely high level of redundancy. We can replicate data in a variety of ways that we would never have been capable of on our own hardware.
- Unstructured data makes it harder to conceptualize what we have but with partners like Panzura that has been a non-issue for us.
- Not always easy to understand the different models or tiers you can pick from when purchasing.
Azure Blob Storage Scorecard Summary
What is Azure Blob Storage?
Azure Blob Storage Pricing
- Has featureFree Trial Available?Yes
- Does not have featureFree or Freemium Version Available?No
- Does not have featurePremium Consulting/Integration Services Available?No
- Entry-level set up fee?No
|Block Blobs||$0.0081||per GB/per month|
|Azure Data Lake Storage||$0.0081||per GB/per month|
|Managed Discs||$1.54||per month|
|Files||$0.058||per GB/per month|
Azure Blob Storage Technical Details