Storage 101: Object storage in a large 3 open clouds

Azure Blob is a Microsoft homogeneous to Amazon’s S3-based intent storage services. Within that, a “blob” is like a bucket as a horizon for influence of objects.

Objects in Blob (from binary vast object, apparently) storage can be accessed around HTTP(S) URL and by users or customer applications around the Azure Storage REST API, Azure PowerShell, Azure CLI, or an Azure Storage customer library that are accessible for mixed languages that embody .Net, Java, Node.js, Python, PHP and Ruby.

You can upload, download, list, pierce and lift out other commands in Azure Blobs regulating a bombard and authority line interface (CLI). Via a API, identical Get, Put, Delete, etc, commands exist as in S3.

Maximum intent distance is 4.7TB.

S3 users can entrance Azure storage around S3 commands by use of collection that embody S3Proxy, that allows applications that use a S3 API to entrance Blob storage.

Meanwhile, (Scality’s) Zenko Connect for Azure provides an S3 API-compatible front-end translator to Azure Blob Storage. 

There is some interoperability between Azure and Google Cloud Storage, with a ability to duplicate information from a latter to a former regulating Azure Data Factory, for example.