Introduction
Azure Cosmos Database one of the Non-Relational NoSQL Database provided by Microsoft and we have another NoSQL Options in Azure like (Data Lake Storage Gen2, Blob Storage, Redis Cache, HBase in HDInsight), also Azure Cosmos Database Supported multiple API like (Core SQL, Mango DB, Cassandra, Graph, Azure Table) IF you need to learn more about this Point Check this Link Choose the appropriate API for Azure Cosmos DB, Azure Cosmos Database supported Write option in multiple regains in the same Database and the synchronizations tacking care about syncing the data. For more information about Azure Cosmos database, I highly recommend you to look into Microsoft Documentation
- How to Provision Azure Cosmos DB Account
- How to Provision Azure Cosmos DB Container
- Load and Explorer the data into Azure Cosmos DB Container
- Replication in Azure Cosmos DB
- Data Consistency in Azure Cosmos DB
- Cosmos DB and open Source
- Azure Cosmos Database Resources
How to Provision Azure Cosmos DB Account
To Create Azure Cosmos Database we need to create First Database account and this like Database instance we can host on it multiple databases, then after this step, we need to create Container ID and this the Database name in this you can find below what is the information required when we need to create Azure Cosmos Database account and for how to do it check below 👇✅ GIF File ✅to know how you can do it and For more information Check this Article
- Account Name: it is like the instance name in SQL Server
- Notebooks: Jupyter notebook is an open-source web application that allows you to create and share documents it is like the Azure Data Studio Notebook For more information read this Article
- Location: The location you need to host on it your Azure Cosmos DB account
- Account Type: It is something like a definition or categorized, we can consider it like Azure Resource Tag.
- Geo-Redundancy: Enabling this Option automatically replicates your data to the region geo-paired with your current region you selected it. For more information about the Region geo-paired check this link Azure Regional Pairs IF you don’t enable it during the setup you can enable it after the configuration from the main overview of the Azure Cosmos Account
- Multi-region Write: Enable the write option on the Regions you selected it on the geo-redundancy this means If you need to enable the Multi Regions Write option you Should Enable the Geo-Redundancy option with it this option you can enable it after the installation from Replicate Data Globally option If you need to learn more about this option check this Link
How to Provision Azure Cosmos DB Container
Now after creating the Azure Cosmos DB account we will configure the first DB Container ID (Database Name) in this Section I highly recommend you to read more about provisioned throughput in Azure Cosmos DB in below 👇✅ GIF File ✅ you will know How to Provision the Azure Cosmos DB Container
Load and Explorer the data into Azure Cosmos DB Container
Load the Explorer the data from Azure Portal you can insert, update, delete and select data into/from Azure Cosmos DB Using Query Explorer For more information About How to use Query Explorer and Data Explorer check Below 👇✅ GIF File ✅
Replication in Azure Cosmos DB
As I mentioned we can enable the Geo-redundancy and Multi-Region Write option during the setup or we can Configure them after the installation from Replicate Data Globally Select the regions you need to replace your Cosmos DB to it then save that’s only
IF you need to Enable the Multi-Region Write you can enable it easily from the same page and it will be enabled on all of the regions you selected it before
Data Consistency in Azure Cosmos DB
Azure Cosmos DB Consistency levels (Strong, Bounded staleness, Session, Consistent Prefix, Eventual) When you have replication between regions you should manage the data Consistency on Azure Cosmos DB based on your case and the app usage for more information check this article
- Strong Consistency level: All of the Data Write into the primary will be available at the same time for readers in all regions and this option very helpful for system link banking system
- Bounded staleness Consistency level: Customize the latency for data availability on regions based on your needs
- Session: Bases on Session IF the user X insert or update data into primary the same user can read it from the other regions on time
- Eventual: No grantee here that the data will be available in all regions at the same time
In the left side select default Consistency and select the option based on your work
Choose the right consistency level on Cosmos Database For more information check this link
Cosmos DB and open Source
Azure Cosmos Database Resources
- Azure Cosmos DB documentation https://docs.microsoft.com/en-us/azure/cosmos-db/
- Welcome to Azure Cosmos DB: https://docs.microsoft.com/en-us/azure/cosmos-db/introduction
- Frequently asked questions about Azure Cosmos DB https://docs.microsoft.com/en-us/azure/cosmos-db/faq
- Common Azure Cosmos DB use cases https://docs.microsoft.com/en-us/azure/cosmos-db/use-cases
- Cosmos DB Pricing Model: https://azure.microsoft.com/en-us/pricing/details/cosmos-db/
- Azure Cosmos DB calculator estimation for the workload cost https://cosmos.azure.com/capacitycalculator/
- Azure Cosmos Emulator for local development and testing https://docs.microsoft.com/en-us/azure/cosmos-db/local-emulator
- Migrate your data to Azure Cosmos DB: https://docs.microsoft.com/en-us/azure/cosmos-db/import-data
- Consistency levels in Azure Cosmos DB https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels
DB Cloud TECH 
