As modern cloud-based apps have evolved, they’ve required data storage to adapt with them. Services such as Azure Cosmos DB have risen to the challenge by providing a fully-managed, multi-model, globally-distributed NoSQL database.
In this hands-on lab scenario, your organization (Awesome Company) is developing a next-generation video game that will rely heavily on the cloud. In order to achieve guaranteed performance around the globe, you’ve chosen Azure Cosmos DB as the data backend. To get started on this project, you’re going to create two different Azure Cosmos DB databases: one to store player profiles, and another to collect session metadata. Since you’ll likely be creating many support databases like the metadata one, you’ll use an ARM template to deploy it.
Performing the actions of this lab will help you become familiar with how to provision Azure Cosmos DB databases, both through the portal and by ARM template.
**Note: It will take a significant amount of time for the deployments to finish. Please make sure you have at least an hour for completion.**
Successfully complete this lab by achieving the following learning objectives:
- Create an Azure Cosmos DB Account for the Players Database
Using the Azure portal, create an Azure Cosmos DB account. Use a unique name such as acgaming-1234.
- Create the Players Database and Container
Within the acgaming-**** account, create a Players database and Profiles container.
- Create the Session Database and Table Using PowerShell and an ARM Template
Use an ARM template to provision a Table API account and a table named Session. A template is provided via a GitHub repo, or you can use one of your own.