Azure blob storage
It is Microsoft's item stockpiling answer for the cloud. Mass capacity is upgraded for putting away an enormous measure of unstructured information, like text or twofold information.
Blob storage usages:
Azure blob stockpiling is basic for the whole Microsoft Azure on the grounds that numerous other Azure administrations will store the information inside a capacity account, inside the mass stockpiling, and follow up on that information. What's more, every mass ought to be put away in a compartment.
The holder is more similar to an envelope where various masses are put away. At the compartment level, we can characterize security strategies and dole out those arrangements to the holder, which will be flowed to every one of the masses under a similar holder.
A capacity record can contain a limitless number of holders, and every compartment can contain a limitless number of masses up to the greatest furthest reaches of capacity account size (up to 500 TB>
To allude this mass, whenever it is set into a holder inside a capacity account, we can utilize the URL, which resembles http://mystorageaccount.blob.core.windows.net/mycontainer/myblob.
Mass capacity depends on a level stockpiling plan. So you can't make a holder inside a compartment. How about we take a model - when we make a compartment like recordings and if we have any desire to separate between proficient recordings and individual recordings. Then, at that point, we can prefix the mass names with staff for individual recordings and expert for proficient recordings. The mass name will be displayed as private video1, individual video2 for individual recordings, and for proficient recordings - proficient video1, proficient video2. Like this, we can make a virtual order, however we can't make a compartment inside a holder inside the Azure mass stockpiling administration.
Azure offers three sorts of mass help:
More often than not, we work with block mass and attach masses. Page masses are made naturally. At the point when we make a virtual machine, the capacity account gets made, and the circles related with the virtual machine will be put away in the capacity account. Yet, for a large portion of the stockpiling arrangements like we know, we are fostering an application like YouTube, or we are fostering a checking application, all things considered, possibly we use block masses or attach masses in light of the necessity.
Naming and Referencing The names of holder and mass ought with comply to certain standards. Since the holder name and mass name will be a piece of the URL when you are attempting to get to them. They need with comply to certain principles which are indicated beneath.
Metadata & Snapshots We can store a few measure of data against a compartment or mass as metadata. It is a name-esteem pair related with the compartment or mass. Metadata names should comply with the name rules for C# identifiers. For instance - when we are fostering any video web based application with backend as Azure mass stockpiling, then, at that point, all things considered, when the client transfers a video, we need to store the client data as metadata against that video. It is extremely valuable once we begin fostering an application in light of mass stockpiling.
Blob Snapshots Depiction is a perused just form of the mass stockpiling. We can utilize previews to make a reinforcement or designated spot of a mass. A depiction mass name incorporates the base mass URL in addition to a date-time esteem that demonstrates when the preview was made. Once more on the off chance that we are fostering a YouTube-like application and need to hold the past variant of the video, then, at that point, we can take a preview of it and store it once the client refreshes the video. In this way, a client like SharePoint can see the past adaptation of the video and this variant of the video.
To get to the depiction, we need to add an inquiry string toward the finish of the URL. What's more, a depiction with a comparable date and time when the preview was made.