Hi! Guys welcome to the continuous article set of my Azure cloud platform based on the shared cloud architecture. This is my 12th article. You can visit my previous articles from the below links:
- 1st article: AZURE CLOUD PLATFORM BASED ON THE SHARED CLOUD ARCHITECTURE
- 2nd article: AZURE CLOUD PLATFORM -Azure Active Directory
- 3rd article: AZURE CLOUD PLATFORM -Authentication
- 4th article: AZURE CLOUD PLATFORM -Subscription
- 5th article: AZURE CLOUD PLATFORM -CDN
- 6th article: AZURE CLOUD PLATFORM -Key Vaults
- 7th article: AZURE CLOUD PLATFORM -Integrate Angular Frond-End Application with Azure AD
- 8th article: AZURE CLOUD PLATFORM -Front Door
- 9th article: AZURE CLOUD PLATFORM -App Services
- 10th article: AZURE CLOUD PLATFORM -Functions
- 11th article: AZURE CLOUD PLATFORM -Database For MySQL Server
An Azure storage account contains all of your Azure Storage data objects: blobs, files, queues, tables, and disks. Each type supports different features and has its own pricing model. Consider these differences before you create a storage account to determine the type of account that is best for your applications. The types of storage accounts are:
- General-purpose v2 accounts: Basic storage account type for blobs, files, queues, and tables. Recommended for most scenarios using Azure Storage.
- General-purpose v1 accounts: Legacy account type for blobs, files, queues, and tables. Use general-purpose v2 accounts instead when possible.
- BlockBlobStorage accounts: Storage accounts with premium performance characteristics for block blobs and append blobs. Recommended for scenarios with high transactions rates, or scenarios that use smaller objects or require consistently low storage latency.
- FileStorage accounts: Files-only storage accounts with premium performance characteristics. Recommended for enterprise or high performance scale applications.
- BlobStorage accounts: Legacy Blob-only storage accounts. Use general-purpose v2 accounts instead when possible.
The storage account provides a unique namespace for your Azure Storage data that is accessible from anywhere in the world over HTTP or HTTPS. Data in your Azure storage account is durable and highly available, secure, and massively scalable.
If you follow my articles in the same order you know that i created a storage when i created MySQL server for my project. If you new to this article without study my last article you can visit follow the site and follow the steps and create your Azure Storage.
This is the end of Article 12 and hope you get a brief idea about Azure Storage.
Will see you on my next article Integrate Spring Boot Backend.