Eric  Bukenya

Eric Bukenya

1624713540

Learn NoSQL in Azure: Diving Deeper into Azure Cosmos DB

This article is a part of the series – Learn NoSQL in Azure where we explore Azure Cosmos DB as a part of the non-relational database system used widely for a variety of applications. Azure Cosmos DB is a part of Microsoft’s serverless databases on Azure which is highly scalable and distributed across all locations that run on Azure. It is offered as a platform as a service (PAAS) from Azure and you can develop databases that have a very high throughput and very low latency. Using Azure Cosmos DB, customers can replicate their data across multiple locations across the globe and also across multiple locations within the same region. This makes Cosmos DB a highly available database service with almost 99.999% availability for reads and writes for multi-region modes and almost 99.99% availability for single-region modes.

In this article, we will focus more on how Azure Cosmos DB works behind the scenes and how can you get started with it using the Azure Portal. We will also explore how Cosmos DB is priced and understand the pricing model in detail.

How Azure Cosmos DB works

As already mentioned, Azure Cosmos DB is a multi-modal NoSQL database service that is geographically distributed across multiple Azure locations. This helps customers to deploy the databases across multiple locations around the globe. This is beneficial as it helps to reduce the read latency when the users use the application.

As you can see in the figure above, Azure Cosmos DB is distributed across the globe. Let’s suppose you have a web application that is hosted in India. In that case, the NoSQL database in India will be considered as the master database for writes and all the other databases can be considered as a read replicas. Whenever new data is generated, it is written to the database in India first and then it is synchronized with the other databases.

Consistency Levels

While maintaining data over multiple regions, the most common challenge is the latency as when the data is made available to the other databases. For example, when data is written to the database in India, users from India will be able to see that data sooner than users from the US. This is due to the latency in synchronization between the two regions. In order to overcome this, there are a few modes that customers can choose from and define how often or how soon they want their data to be made available in the other regions. Azure Cosmos DB offers five levels of consistency which are as follows:

  • Strong
  • Bounded staleness
  • Session
  • Consistent prefix
  • Eventual

In most common NoSQL databases, there are only two levels – Strong and EventualStrong being the most consistent level while Eventual is the least. However, as we move from Strong to Eventual, consistency decreases but availability and throughput increase. This is a trade-off that customers need to decide based on the criticality of their applications. If you want to read in more detail about the consistency levels, the official guide from Microsoft is the easiest to understand. You can refer to it here.

Azure Cosmos DB Pricing Model

Now that we have some idea about working with the NoSQL database – Azure Cosmos DB on Azure, let us try to understand how the database is priced. In order to work with any cloud-based services, it is essential that you have a sound knowledge of how the services are charged, otherwise, you might end up paying something much higher than your expectations.

If you browse to the pricing page of Azure Cosmos DB, you can see that there are two modes in which the database services are billed.

  • Database Operations – Whenever you execute or run queries against your NoSQL database, there are some resources being used. Azure terms these usages in terms of Request Units or RU. The amount of RU consumed per second is aggregated and billed
  • Consumed Storage – As you start storing data in your database, it will take up some space in order to store that data. This storage is billed per the standard SSD-based storage across any Azure locations globally

Let’s learn about this in more detail.

#azure #azure cosmos db #nosql #azure #nosql in azure #azure cosmos db

What is GEEK

Buddha Community

Learn NoSQL in Azure: Diving Deeper into Azure Cosmos DB
Eric  Bukenya

Eric Bukenya

1624713540

Learn NoSQL in Azure: Diving Deeper into Azure Cosmos DB

This article is a part of the series – Learn NoSQL in Azure where we explore Azure Cosmos DB as a part of the non-relational database system used widely for a variety of applications. Azure Cosmos DB is a part of Microsoft’s serverless databases on Azure which is highly scalable and distributed across all locations that run on Azure. It is offered as a platform as a service (PAAS) from Azure and you can develop databases that have a very high throughput and very low latency. Using Azure Cosmos DB, customers can replicate their data across multiple locations across the globe and also across multiple locations within the same region. This makes Cosmos DB a highly available database service with almost 99.999% availability for reads and writes for multi-region modes and almost 99.99% availability for single-region modes.

In this article, we will focus more on how Azure Cosmos DB works behind the scenes and how can you get started with it using the Azure Portal. We will also explore how Cosmos DB is priced and understand the pricing model in detail.

How Azure Cosmos DB works

As already mentioned, Azure Cosmos DB is a multi-modal NoSQL database service that is geographically distributed across multiple Azure locations. This helps customers to deploy the databases across multiple locations around the globe. This is beneficial as it helps to reduce the read latency when the users use the application.

As you can see in the figure above, Azure Cosmos DB is distributed across the globe. Let’s suppose you have a web application that is hosted in India. In that case, the NoSQL database in India will be considered as the master database for writes and all the other databases can be considered as a read replicas. Whenever new data is generated, it is written to the database in India first and then it is synchronized with the other databases.

Consistency Levels

While maintaining data over multiple regions, the most common challenge is the latency as when the data is made available to the other databases. For example, when data is written to the database in India, users from India will be able to see that data sooner than users from the US. This is due to the latency in synchronization between the two regions. In order to overcome this, there are a few modes that customers can choose from and define how often or how soon they want their data to be made available in the other regions. Azure Cosmos DB offers five levels of consistency which are as follows:

  • Strong
  • Bounded staleness
  • Session
  • Consistent prefix
  • Eventual

In most common NoSQL databases, there are only two levels – Strong and EventualStrong being the most consistent level while Eventual is the least. However, as we move from Strong to Eventual, consistency decreases but availability and throughput increase. This is a trade-off that customers need to decide based on the criticality of their applications. If you want to read in more detail about the consistency levels, the official guide from Microsoft is the easiest to understand. You can refer to it here.

Azure Cosmos DB Pricing Model

Now that we have some idea about working with the NoSQL database – Azure Cosmos DB on Azure, let us try to understand how the database is priced. In order to work with any cloud-based services, it is essential that you have a sound knowledge of how the services are charged, otherwise, you might end up paying something much higher than your expectations.

If you browse to the pricing page of Azure Cosmos DB, you can see that there are two modes in which the database services are billed.

  • Database Operations – Whenever you execute or run queries against your NoSQL database, there are some resources being used. Azure terms these usages in terms of Request Units or RU. The amount of RU consumed per second is aggregated and billed
  • Consumed Storage – As you start storing data in your database, it will take up some space in order to store that data. This storage is billed per the standard SSD-based storage across any Azure locations globally

Let’s learn about this in more detail.

#azure #azure cosmos db #nosql #azure #nosql in azure #azure cosmos db

Learn NoSQL in Azure: An overview of Azure Cosmos DB

In this article, we are going to learn Azure Cosmos DB. This article is a part of the series “Learn NoSQL in Azure”, where we will explore all the different types of non-relational databases that are supported in Azure at the moment. Azure is one of the most popular public cloud platforms that has a big market share all over the world. Cosmos DB is a part of the Databases section in Azure that allows customers to create and use NoSQL or non-relational databases and consume these at scale. You can leverage Cosmos DB to build highly scalable and robust cloud-based applications that support modern big data workloads. Let us understand more about what a NoSQL database is all about and how it is different from a relational database. Although this article focuses on the NoSQL related to Azure, it is to be known that other open-source projects support NoSQL databases like Apache Cassandra, etc. However, these topics are out of the scope of this article and we will focus on Azure mostly.

Why do we need a NoSQL Database?

Overall these decades, developers have been using relational database management systems to develop applications across all domains. Even today, relational databases are used heavily in most modern applications. However, as the applications and databases grew in size, it became difficult for the relational databases to scale and the need for highly scalable databases grew. Applications needed to be highly responsive and available most of the time. Due to these requirements, databases had to be scaled and distributed to achieve high performance and low latency.

However, relational databases were based on relationships, and distributing these databases across multiple systems gets very costly, as these relationships had to be maintained across all the nodes within the cluster. These databases are originally architected to run on single servers in order to maintain the integrity of the databases. This meant that relational databases can be scaled vertically but preferably not horizontally. Vertical scaling could be done by increasing the resources available on the server, but it was limited, unlike horizontal scaling. These limitations gave rise to the evolution of the NoSQL databases as these could be scaled both vertically and horizontally without having to worry about keeping relationships intact.

Introduction to NoSQL Databases

As the name suggests, a NoSQL database is basically a non-relational database. It is different from the fact that data in a NoSQL database is stored in documents as opposed to tables in relational database management systems (RDBMS). Since there are no tables in the database, there aren’t any relationships between the different entities within the database. There are many types of NoSQL databases like Key-Value databases, Columnar Databases, Document Database, Graph Databases, etc. The main form of storage in a NoSQL database is JSON. Let us look at how a NoSQL Database looks like.

As you can see in Figure 1, on the left we have two relational tables – “Orders” and “OrderDetails”. And on the right, we have a JSON document that relates to the structure from the tables. This JSON document is known as a single document in a Document Database. The detailed data from the OrderDetails have been incorporated within the same Orders in a nested form. This is a denormalized form of the data and helps in faster reads as compared to reading data from multiple tables. Here, in a NoSQL database, the data is stored in the form of documents, which means we are going to have one single document for each order. In this way, as the orders increase, they can be distributed to multiple nodes and scaled out accordingly. Notice that since the detailed data are nested within the same document, there is no need to maintain complex relationships within the two entities.

#azure #azure cosmos db #nosql

Ikram Mihan

Ikram Mihan

1582683309

An Overview of Azure Cosmos DB

In this article, we will discuss Azure Cosmos DB. We will answer questions such as: What is a Cosmos DB? Why do we need to use the Cosmos DB? We will also learn how to create a new Azure Cosmos DB account using Azure subscriptions, how to create a new database and collection using Azure, and how to add data to the collection.

In this article, we will see the following,

  • What is Azure Cosmos DB?
  • Why do we need to use the Cosmos DB?
  • How to create a new Azure Cosmos DB account using Azure
  • How to create a new database and collection using Azure
  • How to add data to the collection using Data Explorer
  • How to use SQL Query to the collection using Data Explorer
  • How to get Cosmos DB connection string from Azure

Prerequisite

  • Azure Subscriptions

What is Azure Cosmos DB?

Azure Cosmos DB is a globally distributed database service. It supports multi-model approaches such as the document, Key/Value, wide columns and graph databases using APIs.

The list of APIs such as the following:

  • SQL API
  • MongoDB API
  • Graph API
  • Table API
  • Cassandra API

Why do we need to use the Cosmos DB?

Azure Cosmos DB is offering the following items:

  • Global distributions
  • Elastic scale out
  • Guaranteed low latency
  • Five consistency models
  • Comprehensive SLAs

How to create a new Azure Cosmos DB account using Azure

You can learn in this section, how to create a new Azure cosmos database account using the Azure portal with the following guidelines.

Go to open the new browser, you can copy and paste the following URL

https://portal.azure.com/

Then, sign in to the Azure portal using Microsoft Account credentials:

This is image title

After successfully logging into the Azure portal, you can see the dashboard looks like the following screenshot.

This is image title

You can go to create a resource-Databases - click the Azure Cosmos DB.

This is image title

The Azure Cosmos DB new account window will be opened and you can enter the following details, which are required. Then, click the Create button.

ID
API
Subscription Name
Resource Group Name
Location

The list of API options is available in the following screenshot:

This is image title

This is image title

Now, you can see the notification window displaying the deployment in progress notification. Once it is completed you will get the deployment succeeded notification in the notification window. Then, click the go to resource button.

This is image title

This is image title

After successfully creating the Azure Cosmos DB account, the Congratulations! Your Azure Cosmos DB account was created window will be opened, as in the following screenshot.

This is image title

How to create a new database and collection using Azure

You will learn in this section, how to create a new database and collection in Data Explorer using Azure portal.

You can go to Data Explorer - click the New Collections

This is image title

The Add Collection window will be opened and you can enter the following details, which are required. Then, click the OK button.

  • Database Id
  • Collection Id
  • Storage Capacity
  • Throughput

This is image title

You can see the new database and collection looks at the following screenshot.

This is image title

How to add data to the collection using Data Explorer

You can learn in this section, how to add sample data to the collection in Data Explorer using Azure portal at the following guidelines.

You can go to Data Explorer - Expand the Table collection in the Collection window, click the Documents - click the New Document.

This is image title

The new document window will be opened and add the data to the collection with the following format.

This is image title

{  
   “Id”: “1”,  
   “TableName”: “Table A”,  
   “Location”: “Front Row”,  
   “Status”: “Available”,  
   “Date”: “28-02-2018”  
}  

Once you have added json data to the document, click the Save button.

This is image title

After successfully added records to the collection it looks like the following screenshot:

This is image title

How to add SQL Query to the collection using Data Explorer

You can learn in this section, how to use SQL query to the collection in Data Explorer using Azure portal at the following guidelines.

You can go to Data Explorer - Expand the Table collection in the Collection window, click the New SQL Query

This is image title

The Query window will be opened as in the below screenshot

This is image title

Once you have executed query by clicking Execute Query button:

This is image title

You can use the Where condition and Order By for the select statement on SQL Query window in the Azure Cosmos DB as in the below screenshots:

This is image title

This is image title

How to get Cosmos DB connection string from Azure

You will learn in this section, how to get the Cosmos DB connection string in Keys using the Azure portal.

You can go to Settings - click the Keys

This is image title

Now you can copy the URI and Primary Key into your web.config file in your project

Conclusion

I hope you understand now about Azure Cosmos DB, how to create a new Azure Cosmos DB account using Azure, how to create a new database and collection using Azure, how to add data to the collection using Data Explorer, how to use SQL Query to the collection using Data Explorer and how to get Cosmos DB connection string from Azure. I have covered all the required things. If you find anything missing, please let me know. Thank you!

#Azure #Azure Cosmos DB #Cosmos DB

Cody  Osinski

Cody Osinski

1624469280

Understanding how to query arrays in Azure Cosmos DB

This blog is the final part of a series of blogs where we’ll demystify commonly confused concepts for developers learning how to query data using the SQL (core) API in Azure Cosmos DB. Today, we’ll walk through tips and tricks for querying arrays.

Using an example, we’ll show how to use these concepts when querying arrays:

  • Accessing a specific array element
  • Iterating over arrays
  • JOINs
  • Subqueries

Example Scenario:

Nick is a developer that created an app that stores shopping lists. His app is incredibly popular around the holidays and has soared to 1 million active users!

He has a Cosmos container that has the shopping lists modeled as JSON documents. Here’s an example document:

{
  "id": "Tim",
  "city": "Seattle",
  "gifts": [
     {
        "recipient": "Andrew",
        "gift": "blanket"
     },
     {
        "recipient": "Deborah",
        "gift": "board game"
     },
     {
        "recipient": "Chris",
        "gift": "coffee maker"
     }
  ]
}

The remainder of the blog will focus on ways to query arrays, starting with the simplest (and least expressive) and concluding with the more advanced concepts.

#core (sql) api #query #azure cosmos db #azure #cosmos db

Ruthie  Bugala

Ruthie Bugala

1626494129

Using the new C# Azure.Data.Tables SDK with Azure Cosmos DB

Last month, the Azure SDK team released a new library for Azure Tables for .NET, Java, JS/TS and Python. This release brings the Table SDK in line with other Azure SDKs and they use the specific Azure Core packages for handling requests, errors and credentials.

Azure Cosmos DB provides a Table API offering that is essentially Azure Table Storage on steroids! If you need a globally distributed table storage service, Azure Cosmos DB should be your go to choice.

If you’re making a choice between Azure Cosmos DB Table API and regular Azure Table Storage, I’d recommend reading the following article.

In this article, I’ll show you how we can perform simple operations against a Azure Cosmos DB Table API account using the new Azure.Data.Table C## SDK. Specifically, we’ll go over:

  • Installing the SDK 💻
  • Connecting to our Table Client and Creating a table 🔨
  • Defining our entity 🧾
  • Adding an entity ➕
  • Performing Transactional Batch Operations 💰
  • Querying our Table ❓
  • Deleting an entity ❌

Let’s dive into it!

Installing the SDK 💻

Installing the SDK is pretty simple. We can do so by running the following dotnet command:

dotnet add package Azure.Data.Tables

If you prefer using a UI to install the NuGet packages, we can do so by right-clicking our C## Project in Visual Studio, click on Manage NuGet packages and search for the Azure.Data.Tables package:

Connecting to our Table Client and Creating a table 🔨

The SDK provides us with two clients to interact with the service. A TableServiceClient is used for interacting with our table at the account lelvel.

We do this for creating tables, setting access policies etc.

We can also use a TableClient. This is used for performing operations on our entities. We can also use the TableClient to create tables like so:

TableClient tableClient = new TableClient(config["StorageConnection"], "Customers");
            await tableClient.CreateIfNotExistsAsync();

To create our Table Client, I’m passing in my storage connection string from Azure and the name of the table I want to interact with. On the following line, we create the table if it doesn’t exist.

To get out Storage Connection string, we can do so from our Cosmos DB account under Connection String:

When we run this code for the first time, we can see that the table has been created in our Data Explorer:

Defining our entity 🧾

In Table Storage, we create entities in our table that require a Partition Key and a Row Key. The combination of these need to be unique within our table.

Entities have a set of properties and strongly-typed entities need to extend from the ITableEntity interface, which expose Partition Key, Row Key, ETag and Timestamp properties. ETag and Timestamp will be generated by Cosmos DB, so we don’t need to set these.

For this tutorial, I’m going to use the above mentioned properties along with two string properties (Email and PhoneNumber) to make up a CustomerEntity type.

#csharp #programming #azure #data #azure cosmos db #azure