Deep Dive into Azure Storage Blobs, Disks, Files, Tables and Queues

Play Deep Dive into Azure Storage Blobs, Disks, Files, Tables and Queues
Sign in to queue

Description

Azure Storage is a highly scalable, available, and durable cloud storage system that stores 30+ trillion objects and serves 3.5+ million requests per second on average. It provides abstractions like Blobs, Files, NoSQL Tables and Queues as well as IaaS data disks —all built on top of the same framework. This talk gives an overview of Azure Storage and the different abstractions. We will dive deeper into Azure data disks which are the underpinning of persisted data in IaaS VMs as well as Azure Files which are ideal for migrating existing applications that rely on network file shares. We will also provide details on Azure Premium Storage Disks, our disk solution for demanding workloads that require consistent, low latency and high IOPs.

 

Day:

2

Embed

Download

The Discussion

  • User profile image
    gduncan411

    @tonig: The live stream does not start for another hour (and this session in two hours) Please see https://channel9.msdn.com for the stream and the countdown

  • User profile image
    Ron Wright

    What file systems are used under the covers? Given that page blobs are sparse, this implies the use of NTFS. What about ReFS?

  • User profile image
    RobMer

    Asking all this here because of "Sorry, something has gone wrong. Your question was not submitted" error while trying to ask during live session... :'(

    Q1: Does shares on Azure Files allow some kind of scaling of resources (like SOFS based shares) ?

    Q2: Is any kind of resiliency (à la ReFS) currently to be expected for data copied on Azure Files or Disks (unless maybe possibly only projected for some future) even if not enabling any of other available durability options (LRS, ZRS, etc) ?

    TIA

  • User profile image
    Ron Wright

    VSS supports the snapshotting of shares. Why not Azure Files?

  • User profile image
    RicksterCDN

    @Ron Wright: we are not using native file system that requires a server in order to serve up Azure files. this solution is client agnostic.

  • User profile image
    RicksterCDN

    @RobMer: Q1 it is not based on SOFS, but is readily available to all VM or PaaS resources to use, if they have access and credentials to the share.

    Q2: resiliency is provided at the lower level where three copies of the data is stored within the datacenter and can be geo-replicated if configured to do so.

  • User profile image
    RicksterCDN

    @Ron Wright: I don't believe we are sharing that level of information at this time.

  • User profile image
    artisticche​ese

    What tool was used to measure IOPS?

  • User profile image
    miteshc

     Hi great demo and session. 

    GT65345, the tool was IOMETER.

    It would be great to know / show us what the workload settings actually were to get some context around those IOPS.

    Thanks

Add Your 2 Cents