Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Guide to NoSQL with Azure Cosmos DB

You're reading from   Guide to NoSQL with Azure Cosmos DB Work with the massively scalable Azure database service with JSON, C#, LINQ, and .NET Core 2

Arrow left icon
Product type Paperback
Published in Sep 2018
Publisher Packt
ISBN-13 9781789612899
Length 214 pages
Edition 1st Edition
Languages
Tools
Concepts
Arrow right icon
Authors (2):
Arrow left icon
Gaston C. Hillar Gaston C. Hillar
Author Profile Icon Gaston C. Hillar
Gaston C. Hillar
Daron Yöndem Daron Yöndem
Author Profile Icon Daron Yöndem
Daron Yöndem
Arrow right icon
View More author details
Toc

Table of Contents (9) Chapters Close

Preface 1. Introduction to NoSQL in Cosmos DB 2. Getting Started with Cosmos DB Development and NoSQL Document Databases FREE CHAPTER 3. Writing and Running Queries on NoSQL Document Databases 4. Building an Application with C#, Cosmos DB, a NoSQL Document Database, and the SQL API 5. Working with POCOs, LINQ, and a NoSQL Document Database 6. Tuning and Managing Scalability with Cosmos DB 7. Answers 8. Other Books You May Enjoy

Understanding the options for provisioning request units


So far, we have been provisioning throughput for each collection. This gives us more granular control on how many request units we will need per container. This option is usually better if you have a smaller number of containers and require guaranteed throughput on each container backed by SLA. Keep in mind that all physical partitions of a Cosmos DB container will equally share the number of request units available for the container.

The other option is to provision throughput at the database level. In this case, all the containers within the database will share the total pool of request units you have. This can be a more comfortable management option when you have a high number of containers and do not necessarily want to manage all individually.

Note

One crucial difference between container-level provisioning and database-level provisioning is the minimum throughput we can provision. For partitioned containers, the minimum provisioned...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime