Microsoft Azure Object Storage Reviews

I use this tool to develop Blob storage and deploy it on Azure. We are working in the educational domain and this solution is used in campus management.

The most valuable features are the development and redundancy.

This solution is easy to use, and performance-wise it is better than others.

Object re-use should be improved in order to get better performance and reduce the cost.

We have experienced performance issues on the website.

The interface on the homepage can be improved.

When we are uploading items into storage, we only get information from a high level. This makes it difficult to find and delete specific files.

I have been using this solution for about two years.

In terms of stability, I have not found any issues.

There are no issues with scalability. We have approximately 400,000 users who are students, as well as others.

We were in touch with technical support to address slowdowns that were occurring on the website.

The initial setup is straightforward.

I deployed this solution.

The cost is based on the amount of traffic and we paid approximately 18 lakh Rupees ($25,000 USD) last year.

I recommend using this tool as it is useful and very easy to implement. Any develop can help to reduce their costs.

I would rate this solution an eight out of ten.

Our architects are using it, mostly. We primarily use the solution for Docker containers that we host our Jira and Confluence on. We use the solution for storage, including File, Table, and Block. We have about 20 terabytes of storage. We also do some reporting.

The metadata that the solution provides is quite valuable for us. If we need to analyze the latest data from a particular department or particular user, we can simply query through the metadata we store in Azure Object Storage and simply fetch those records which are maybe one day or one month old. this metadata storage is really handy for us.

We've seen some performance issues with Azure Table storage. It's quite slow. The performance surrounding it should be improved to speed things up a bit.

Moving data from cold storage to the hot storage, or, to put it another way, moving data back and forth between regular storage and archival storage is difficult. There's no easy way to do it. In the past, we've been required to download the data and then upload it to cold storage. It's an annoying process. If the solution could fix this it would be much better.

I believe I have been using the solution for four years.

The solution is quite stable. We haven't had any issues with it.

We have people who use the solution on a daily basis in our organization. There are about 50 or more users.

It's quite easy to scale the solution as needed.

Technical support has been good. Whenever we've raised requests they've been dealt with promptly. We're satisfied with the level of support given to us.

We didn't previously use another solution before implementing Object Storage. Previously we had everything in-house. Now everything is on the public cloud.

The initial setup for the solution is straightforward. It's simple, in fact. It's not complex at all. Deployment is fast and easy too. It only takes about 20 minutes.

In our company, the maintenance of the solution is outsourced. We have a team of four outside the organization that handles it for us. They're like a support team and handle everything 24/7.

The implementation was handled completely in-house. We have Azure certified architects in my organization and we simply raise the request for the types of storage we want, what sort of machine we want and I handle the approvals.

I'm not sure which version of the solution we are currently using.

In terms of if other organizations should use the solution, I'd say that the question is, do they understand what they prefer. They need to understand the data they want to store and if they will need regular access to it. If they need the data to be easily accessible daily, they need to go for a Hot Tier. If they feel like they would be better off archiving, they need to look for a Cold Tier. The difference between the two is huge.

I'd rate the solution seven out of ten.

Object Storage's best features are the soft delete option and the retention period.

I've been using Object Storage for a year.

Object Storage is stable.

Object Storage is scalable.

Azure's technical support could be better - they take a long time to respond, and issues get transferred to multiple engineers, so you have to repeat the whole story every time without getting any proper resolution.

Neutral

The initial setup was simple.

Object Storage is competitively priced.

Object Storage is easy to use, very portable, and easy to integrate. I would rate it as nine out of ten.