In this article we will learn what is Cosmos DB, review general concepts, features and key points for capacity calculation when creating new Database.
If you are already familiar with concepts and architecture feel free to explore other articles from the series:
Recently I read an interesting and provocative article on Medium, which gained the required attention from readers.
It’s a short one — read it to get a feeling of why I’m laying out these obvious points to you now.
For those who have no time, my interpretation of the article: Author doesn’t see a reason to follow test-driven development and considers it as one of the unnecessary ceremonies of software craftsmanship tribe.
And to be fair TDD can be annoying. I’m not following it for every single piece of code. I don’t push my team to write unit tests for…
In the first part of the partitioning story, we reviewed key concepts and considerations to take into account when designing Cosmos DB as a container for your NoSQL data:
Please check other parts from the series of articles on Cosmos DB for developers:
This article will walk through a process of hands-on validation of logical partitioning strategy. …
In a previous article, we reviewed how to set up logs and troubleshoot Cosmos DB issues using Azure Log Analytics.
Feel free to explore other articles of the series:
You can read the full story by navigating to the link above. In a nutshell, I pushed 31 million Invoices into Cosmos DB with a total size reaching 47GBs. The database had containers with different indexing and logical partition key configuration. …
In this, another part of the series, we already know how to set up an account, what’s the difference between the Serverless and Provisioned throughput.
We will learn the types of monitoring available in Cosmos DB and then set up the Log Analytics workspace and troubleshoot the physical partition split event.
This article is a part of the series. Check the below articles before proceeding to log analysis:
Cosmos DB as…
This article is a part of the series. Check others for more details around Cosmos DB:
Cosmos DB is designed to scale horizontally based on the distribution of data between physical partitions (PP). Think of it as separately deployable self-sufficient nodes which are synchronized and coordinated by a central gateway.
The second essential part of the architecture is the logical partition (LP) — it’s bucket of documents which share the same…