Hello. In this lesson, you will learn about the Azure Cosmos Database. You'll explore common scenarios for using a Cosmos Database. We will look at common scenarios where developers would choose different APIs, and finally, how to look at the Cosmos Database through the SDK in use at the command line. In this lesson, I will show you what the Azure Cosmos Database is and common solutions for using the Cosmos Database. Cosmos Database is a new Cloud -based database architecture for large -scale distributed applications. Cosmos Databases can be spread throughout the Azure environment and provides very high reliability and very high performance. Cosmos Database can scale to dramatic amounts of records and is a good choice for very large enterprise applications or large -scale commercial applications. The Cosmos DB is a NoSQL database, but can also perform as a relational database. That makes the Cosmos DB a very flexible resource for programmers who want to build enterprise scalable applications, but need potentially different APIs based upon existing knowledge or needs of their current application. The scalability of the Cosmos Database is its primary feature. It is a way to scale and replicate different sections of a database or what could be called shards of a database across many different regions in the Azure environment. This allows you to store data near the customers that will need it, but also allow your application to grow exponentially based on use. You can see the serverless application architecture means you do not have to declare specific machines or pay for dedicated computers. You build on what is called a serverless architecture, which allows it to scale as your needs grow. This provides a flexible way for developers to build applications that may have unpredictable workloads or spiked traffic, where there are large influxes of information periodically. Because the Cosmos DB is primarily a data storage concept, there are many different ways to interact with the Cosmos DB database files. We call these the different APIs. APIs are programmer -specific and they allow programmers to pick technologies that they are familiar with or technologies that support the architecture demands of the application they're building. For example, the PostgreSQL is a popular open -source SQL -based API for programmers who need to read and write information to traditional relational databases. While the Cosmos DB is not a traditional SQL database, Azure provides an SQL -based API that is compliant with the PostgreSQL standard. This allows developers to have transparent access to the global scalable Cosmos DB and use that database as if it was a traditional PostgreSQL database. You can see here in this architecture diagram that we are able to execute commands against the Postgre database as if it was a single resource. The Azure Cosmos DB API intercepts this information and converts this into the underlying structure of the Cosmos database. This means that the API of PostgreSQL is transparent to the developer. The application does not know that it is using Cosmos DB. This is also true for applications that need the MongoDB API. For developers who are developing with the MongoDB API, they can also take advantage of the Cosmos DB and its scalable global architecture and have this be transparent to the developer and the application who's using it. This allows developers to use MongoDB in their applications if they need a document -based database. Cosmos DB has become a very flexible, scalable new way to store distributed information throughout the Cloud using a variety of the APIs that you see at the top of this table. This allows the Cosmos DB to store four different types of data. Traditional key -value pairs that you would see in an SQL database, column family architecture, hierarchical document databases, or graph databases. You can see the variety of APIs at the top of the screen, including traditional SQL, JavaScript, Gremlin, a simple data table API, or the MongoDB. Stay tuned for the next lesson where I'll show you how to create a Cosmos database and select the appropriate API for your application architecture. Thanks for watching.