Microsoft Azure – Use metadata
Azure Blob storage is a service for storing large amounts of unstructured data, such as text or binary data, that can be accessed from anywhere in the world via HTTP or HTTPS. You can use Blob storage to expose data publicly to the world, or to store application data privately.
Common uses of Blob storage include:
– Serving images or documents directly to a browser
– Storing files for distributed access
– Streaming video and audio
– Performing secure backup and disaster recovery
– Storing data for analysis by an on-premises or Azure-hosted service
Blob Addressing format:
URL format: Blobs are addressable using the following URL format: http://
The following example URL could be used to address one of the blobs in the diagram above:
The Blob service contains the following components:
The blob service supports head requests, which can include metadata about the blob. For example, if your application needed the EXIF (Exchangeable Image File) data out of a photo, it could retrieve the photo and extract it.
To save bandwidth and improve performance, your application could store the EXIF data in the blob’s metadata when the application uploaded the photo: you can then retrieve the EXIF data in metadata using only a HEAD request, saving significant bandwidth and the processing time needed to extract the EXIF data each time the blob is read. This would be useful in scenarios where you only need the metadata, and not the full content of a blob. Note that only 8KB of metadata can be stored per blob
EXIF- stands for Exchangeable Image File, and the data provided can be stored to JPEG, RAW and TIFF image file formats.
Azure Import/Export Service
For very large volumes of data (more than 1TB), the Azure Storage offers the Import/Export service, which allows for uploading and downloading from blob storage by shipping hard drives. You can put your data on a hard drive and send it to Microsoft for upload, or send a blank hard drive to Microsoft to download data. You can read more about it here. This can be much more efficient than uploading/downloading this volume of data over the network.
Read More: Microsoft – Blob Storage
Uploading Blob Fast
To upload blobs fast, the first question to answer is: are you uploading one blob or many? Use the below guidance to determine the correct method to use depending on your scenario.
Uploading one large blob quickly
To upload a single large blob quickly, your client application should upload its blocks or pages in parallel (being mindful of the scalability targets for individual blobs and the storage account as a whole). Note that the official Microsoft-provided RTM Storage Client libraries (.NET, Java) have the ability to do this. For each of the libraries, use the below specified object/property to set the level of concurrency:
.NET: Set ParallelOperationThreadCount on a BlobRequestOptions object to be used.
Java/Android: Use BlobRequestOptions.setConcurrentRequestCount()
Node.js: Use parallelOperationThreadCount on either the request options or on the blob service.
C++: Use the blob_request_options::set_parallelism_factor method.
note: Blob data gathered from Azure Site
Read about NetApp Products: Click Here
— Bahram Khandan (@PivotalStorage) November 9, 2014
Read more about VMware Virtualization for Dummies 2.0
Published by Wiley, this VMware Special Edition of Virtualization 2.0 For Dummies can be downloaded click Here to Download:
Read More: Amazon Web Services (AWS)