Microsoft Azure Infrastructure Services for Architects by John Savill

Author:John Savill
Language: eng
Format: epub
ISBN: 9781119596547
Publisher: Wiley
Published: 2019-09-25T14:00:00+00:00

DNS is used for the Azure Storage namespace, which is why when talking about Azure Storage accounts and services, you will see the following format:

http(s)://<account>.<service>.core.windows.net/<partition>/object

Using Storage Accounts and Types of Replication

I’ve already referred to storage accounts, so it’s important to understand what a storage account is, how Azure limits storage accounts, and how to choose your storage account design. All data stored in Azure Storage is stored in a storage account. It should be noted that when dealing with VMs, you typically don’t deal with storage accounts. You used to, as the VHD files for VMs were stored in page blobs, which were stored in storage accounts, which required tracking of the number of VHDs per storage account to ensure limits of the storage account did not impact performance and also had challenges when you wanted to change the performance tier. All this was solved with managed disks (covered later), which abstracted away the storage account (it’s still there but basically hidden from you) and made disks a first-class Azure resource. It is still useful to understand storage accounts because even when you are dealing with infrastructure, the capabilities of storage accounts may be useful.

A storage account has a number of attributes:

Each account must have a name that is unique across all of Azure Storage namespace. Azure Storage can be accessed using URLs, and the name you specify is a component of the URL.

Each account must belong to a subscription.

Each account must be created in a particular region. For best performance, you try to keep the location of the storage account in the same region as the service using it.

Each account must specify the replication to be used for the content.

Each account has a performance type—for example, standard (HDD-based) or premium (SSD-based).

A default access tier is specified, hot or cool (this impacts costs related to storage and transactions), but can also be set per object for most account types.

Storage accounts have a type, such as general-purpose v1, v2, blob storage, or file storage.

Each account has a maximum number of IOPS. The Azure storage limits page should be checked for exact, current values, as they do change.

Each account also has size, ingress, and egress limits.

Each account has a set of URL endpoints that are used to access the storage. The URL includes the name specified during creation. A different URL is used for each of the four types of storage services available: Blobs, tables, queues, and files. The URLs use the following format:

https://<storage account name>.<storage service>.core.windows.net

For example, https://savillstorage.blob.core.windows.net/ would be my BLOB endpoint. You can add custom URLs to access storage accounts. Custom URLs are documented at: https://docs.microsoft.com/en-us/azure/storage/blobs/storage-custom-domain-name

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.