Microsoft Azure vs. Google Cloud
BLOB STORAGE
Blob storage is a feature that allows you to store arbitrarily large amounts of unstructured data such as audio, images, video, scripts, and text, and serve them to users over HTTP and HTTPS.
I used blob storage mostly to store JavaScript files that were used in SharePoint apps and websites. At first, as I worked with Microsoft technology and I learned Azure, I used Azure. All until I opened a Google Cloud console and thought, - this is better.
Better, - easier to use, requires less steps to complete the action
Better, - easier to use, no prerequisites
Better, - easier to use, interface is clean, contains only features and links you need
Better, - more intuitive naming conventions - a Google's "bucket" is better than Microsoft's "container" alone for the reason of it being too similar to a notion of containers such as Docker container
Better, - pricing, the cost is visible
Better, - Google Cloud Shell where you can script your actions is quite cool
Let's start from scratch - I will create a folder-like place for my files, a blob storage. Then I will try to add a file.
Let's see what the difference between Google Cloud and Azure is.
On Google Cloud,
the step by step guide has three steps:
1. Open Google console and select Storage from the left menu
2. Click on "Create a bucket" - there is virtually nothing else on the page, you can't miss it
3. Enter the name and click on "Create" - check out those price details :-)
On Azure,
there is more than three steps. You need a storage account and resource group as prerequisites.
1. Open the Azure portal and select All services.
2. In the list of resources, type Storage Accounts. As you begin typing, the list filters based on your input. Select Storage Accounts.
3. On the Storage Accounts window that appears, choose Add
4. Select the subscription in which to create the storage account
5. Under the Resource group field, select Create new. Enter a name for your new resource group, as shown in the following image
6. Click on "Review and Create"
7. On validation page, click on "Create"
OK, I created a "chokostorage" storage account - ready to create a container, somewhere, somehow
8. Click on the storage account (chokostorage)
9. Click on "Blobs"
10. Click on "+ Container" and write a name of the container
11. Click on Create button
Now that we have a bucket on Google Cloud and a container on Azure, - what a difference, the score is:
Google Cloud 3 steps
Azure 11 steps
And mind a little detail, no information about the pricing on Azure.
Yeah, with storage account, resource group and all the pages full of links and buttons, who has time to think about the cost..
OK. Cool, I'm ready to add a file.
On Google Cloud:
1. Open the "bucket" page
2. Click on "upload files" and browse to your file
3. Click on "..." and select "Edit permissions"
4. Add "allUsers" if you want public read access
I added a text file and made it public:
Now I can click on a link icon next to "Public" and see my file:
Now I'm adding a file on Azure:
1. I clicked on the container that I made previously and this page opened
2. Click on "Upload" and browse to the file
I got an error. There was a message shown for a second - I didn't have time to read
I'll try with the text file..
That one worked better, I have my .txt file on Azure:
I copied the URL and opened a new browser tab:
What's the score? Well, Azure failed to upload the image. Google cloud wins this one too.
So, what to do with multiple files?
On Google Cloud
Google Cloud has a cool console feature called Cloud Shell that works seamlessly right there in a browser. So I clicked on the " >_ " icon in the top right corner:
For example, to list the contents of the bucket, I write:
gsutil ls gs://choko-bucket
On Azure,
well, you can't do that on Azure. Not in browser.
In summary:
RESULT for Google Cloud vs. Azure:
Google Cloud is a winner by knockout.
Ingen kommentarer:
Send en kommentar