Microsoft's Blob Storage system on Azure is designed to make unstructured data available to customers anywhere through REST-based object storage.
$0.01
per GB/per month
Google Cloud Storage
Score 9.0 out of 10
N/A
Google Cloud Storage is unified object storage for developers and enterprises.
N/A
Google Compute Engine
Score 8.7 out of 10
N/A
Google Compute Engine is an infrastructure-as-a-service (IaaS) product from Google Cloud. It provides virtual machines with carbon-neutral infrastructure which run on the same data centers that Google itself uses.
$0
per month GB
Pricing
Azure Blob Storage
Google Cloud Storage
Google Compute Engine
Editions & Modules
Block Blobs
$0.0081
per GB/per month
Azure Data Lake Storage
$0.0081
per GB/per month
Files
$0.058
per GB/per month
Managed Discs
$1.54
per month
No answers on this topic
Preemptible Price - Predefined Memory
0.000892 / GB
Hour
Three-year commitment price - Predefined Memory
$0.001907 / GB
Hour
One-year commitment price - Predefined Memory
$0.002669 / GB
Hour
On-demand price - Predefined Memory
$0.004237 / GB
Hour
Preemptible Price - Predefined vCPUs
0.006655 / vCPU
Hour
Three-year commitment price - Predefined vCPUS
$0.014225 / CPU
Hour
One-year commitment price - Predefined vCPUS
$0.019915 / vCPU
Hour
On-demand price - Predefined vCPUS
$0.031611 / vCPU
Hour
Offerings
Pricing Offerings
Azure Blob Storage
Google Cloud Storage
Google Compute Engine
Free Trial
Yes
No
Yes
Free/Freemium Version
No
No
Yes
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
Prices vary according to region (i.e US central, east, & west time zones). Google Compute Engine also offers a discounted rate for a 1 & 3 year commitment.
More Pricing Information
Community Pulse
Azure Blob Storage
Google Cloud Storage
Google Compute Engine
Considered Multiple Products
Azure Blob Storage
Verified User
Contributor
Chose Azure Blob Storage
Azure Blob Storage was used only because we were already using it for other projects, and it has a good reputation for being a reliable cloud provider. It also has widespread regional availability and allows for data replication. It can also be easily accessed via the API or by …
We chose Google Cloud Storage for its superior integration with BigQuery and AI/ML tools. Unlike AWS S3’s complex tiering or Azure’s offline archive, Google Cloud Storage offers millisecond access even for archival classes. This simplified our architecture while providing the …
The two services are very comparable, but we have many different services that all run on the Google Cloud Platform and therefore Google Cloud Storage made more sense as our storage solution rather than looking to an outside service like S3. Either one of these options would …
The perfect blend of setup flexibility, costing and trust of Google could be my answer to the comparison. This being a server backed service so, ruling out the functions. The Setup flexibility and speed set the GCE apart from Kubernetes. Compliance, regulation and the security …
We have used a few other cloud providers of similar services and continue to use Google Compute Engine because it fits well within our technology stack and is cost-effective while providing the service we need. It has allowed us to use and experiment with many more …
App Engine is somewhat similar, but we use it together with Compute Engine. App Engine is good for serving end requests to users -- it can scale automatically to any number of requests, but has it's own limitations. Compute Engine does not have any limitations. but you have to …
Google App Engine is slower in comparison, and costs more than Google Compute Engine. We chose Google Compute Engine because Google App Engine was way too slow (mainly due to having to use Google Cloud Storage).
In Azure, it is the storage to use, and in my view, the Blob Storage offers more, or finer-grained configuration options, than S3. So my recommendation would be to check in detail what is offered. As the Blob Storage is more or less a Microsoft exclusive product, the "interoperability" is more limited than, for example, with S3. The S3 is more widely adopted, and if you cannot exclude a migration scenario from one cloud provider to another, additional effort is needed.
[Google Cloud Storage is] great for storing and playing large video files, and even sharing them securely with others, whether or not they are part of your organization. No need to download video files before watching, and can also be used to store any other kinds of files.
You can use Google Cloud Compute Engine as an option to configure your Gitlab, GitHub, and Azure DevOps self-hosted runners. This allows full control and management of your runners rather than using the default runners, which you cannot manage. Additionally, they can be used as a workspace, which you can provide to the employees, where they can test their workloads or use them as a local host and then deploy to the actual production-grade instance.
Really great, easy to use interface helps us manage files easily. Storage is fast and inexpensive, so we don't have to spin up storage instances locally
Great set of command-line tools to manage data and storage options via scripts and apps, as well as an SDK means we can build GCS into our orchestration and operations tools
Robust integration with other Google cloud tools means that we don't have to think too hard about using GCS for a variety of storage tasks as we interact with other Google services.
Scaling - whether it's traffic spikes or just steady growth, Google Compute Engine's auto-scaling makes sure we've got the compute power we need without any manual juggling acts
Load balancing - Keeping things smooth with that load balancing across multiple VMs, so our users don't have to deal with slow load times or downtime even when things get crazy busy
Customizability - Mix and match configs for CPU, RAM, storage and whatnot to suit our specific app needs
after all of the investment made in the tool and considering how many teams use it I think we would not be likely to move away from this tool. A lot of our information including historical is already here and we are happy with the capabilities of the tool currently
Its pretty good, easy and good performance. Also, interface is very good for starters compared to competitors. Infra as Code (IaC) using Terraform even added easiness for creation, management and deletion of compute Virtual Machines (VM). Overall, very good and very easy cloud based compute platform which simplified infrastructure, very much recommend.
Blob storage is fairly simple, with several different options/settings that can be configured. The file explorer has enhanced its usability. Some areas could be improved, such as providing more details or stats on how many times a file has been accessed. It is an obvious choice if you're already using Azure/Entra.
Very easy to use. I love having my data backed up. I love that Google Cloud Storage provides me with the peace of mind that I no longer need to worry about my data being lost. I can now sleep better at night. Google Cloud Storage is very easy to use. Overall, you save time and have less stress by using Google Cloud Storage.
Having interacted with several cloud services, GCE stands out to me as more usable than most. The naming and locating of features is a little more intuitive than most I've interacted with, and hinting is also quite helpful. Getting staff up to speed has proven to be overall less painful than others.
Google Compute Engine works well for cloud project with lesser geographical audience. It sometimes gives error while everything is set up perfectly. We also keep on check any updates available because that's one reason of site getting down. Google Compute Engine is ultimately a top solution to build an app and publish it online within a few minutes
For performance i give Google Cloud Storage 10 of 10 on performance because even though there are other softwares that do exactly the same thing as Google Drive, it still works exceptionally well. It is very fast, and and far as integration, the only software I have used with it that integrated was Google Docs, and of course it integrates perfectly.
It works great all the time except for occasional issues, but overall, I am very happy with the performance. It delivers on the promise it makes and as per the SLAs provided. Networking is great with a premium network, and AZs are also widespread across geographies. Overall, it is a great infra item to have, which you can scale as you want.
Microsoft has improved its customer service standpoint over the years. The ability to chat with an issue, get a callback, schedule a call or work with an architecture team(for free) is a huge plus. I can get mentorship and guidance on where to go with my environment without pushy sales tactics. This is very refreshing. Typically support can get me to where I need to be on the first contact, which is also nice.
We have never used official support from Google for our Google Cloud Storage, but there is plenty of documentation in place already. With a small amount of work, anybody should be able to get started. Once needs get more complicated, there is still documentation from Google, but also plenty of community support for common use cases around the internet.
The documentation needs to be better for intermediate users - There are first steps that one can easily follow, but after that, the documentation is often spotty or not in a form where one can follow the steps and accomplish the task. Also, the documentation and the product often go out of sync, where the commands from the documentation do not work with the current version of the product.
Google support was great and their presence on site was very helpful in dealing with various issues.
overall I was not directly involved but hears the teams were satisfied with the implementation. the teams that used the tool did not encounter major issues, it was as expected with minor issues and bugs that were resolved later. The more significant learning curve was actually starting to use the tool
Azure Premium Blob offers better latency than competitors. It works best with the Azure ecosystem, and competitors lack it. Azure Blob even stands out in storage durability, providing up to 16 nines. It can have various use cases that can suit all the organisation's needs. The Azure Blob solution can also be deployed on-premises.
We prefer Google Cloud Storage over Amazon Web Services because of the tools and code integration offered by Google Cloud Storage. We found the Google Cloud Storage toolset to be highly usable and give us the fine-grained control we need for managing digital assets. Ultimately, we chose Google Cloud Storage because we found the API and suitability for code integration with our Java codebase to be impeccable and because we had excellent direct support from the Google Cloud Storage team
Google Compute Engine provides a one stop solution for all the complex features and the UI is better than Amazon's EC2 and Azure Machine Learning for ease of usability. It's always good to have an eco-system of products from Google as it's one of the most used search engine and IoT services provider, which helps with ease of integration and updates in the future.
It has assisted greatly with our ability to share documents/information cross functionally. Especially within our advertising team, we store a large amount of information to assist new hires and refresh current employees.
Something that could improve is employees' understanding of how to best utilize Google Cloud Storage. This could improve by implementing a potential training video or tutorial.
Overall, Google Storage has been great. I have not used a similar storage product that had the same enterprise level capabilities.