<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NoSQL on The Coders Blog</title><link>https://thecodersblog.com/tag/nosql/</link><description>Recent content in NoSQL on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 06 May 2026 22:26:38 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/nosql/index.xml" rel="self" type="application/rss+xml"/><item><title>Microsoft Dev: Azure Cosmos DB Conf 2026 Recap: Lessons from Production</title><link>https://thecodersblog.com/azure-cosmos-db-production-lessons-2026-2026/</link><pubDate>Wed, 06 May 2026 22:26:38 +0000</pubDate><guid>https://thecodersblog.com/azure-cosmos-db-production-lessons-2026-2026/</guid><description>&lt;p&gt;You provisioned Azure Cosmos DB with ample Request Units (RUs), your application&amp;rsquo;s P99 latency is creeping up, and throttling errors are becoming more frequent. Sound familiar? This isn&amp;rsquo;t a capacity problem; it&amp;rsquo;s a design problem. The Azure Cosmos DB Conference 2026 made one thing brutally clear: the platform exposes your data modeling and partition key choices like a harsh spotlight.&lt;/p&gt;
&lt;h2 id="the-unseen-bottleneck-partition-keys-and-skewed-distribution"&gt;The Unseen Bottleneck: Partition Keys and Skewed Distribution&lt;/h2&gt;
&lt;p&gt;The single most impactful decision you make for Cosmos DB is the partition key. Forget throwing more RUs at the problem; if your partition key leads to skewed distribution, you&amp;rsquo;re battling hot partitions. This results in 100% RU utilization on some physical partitions while others languish, leading to relentless throttling and unacceptable latency spikes, even if your aggregate RU usage appears low.&lt;/p&gt;</description></item></channel></rss>