{"id":10367,"date":"2025-05-21T08:00:20","date_gmt":"2025-05-21T15:00:20","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/cosmosdb\/?p=10367"},"modified":"2025-05-16T08:24:13","modified_gmt":"2025-05-16T15:24:13","slug":"now-in-preview-azure-cosmos-db-fleets","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cosmosdb\/now-in-preview-azure-cosmos-db-fleets\/","title":{"rendered":"Now in Preview: Azure Cosmos DB Fleets"},"content":{"rendered":"

We\u2019re excited to announce the preview of Azure Cosmos DB fleets<\/strong>.<\/p>\n

Azure Cosmos DB fleets address common challenges that developers face when building and managing multi-tenant or Software as a Service (SaaS) applications.<\/p>\n

Today, many SaaS providers using Azure Cosmos DB isolate each tenant in a separate database account to meet strict performance and security requirements\u2014for example, supporting customer-managed keys. While this approach ensures tenant isolation, it creates operational complexity at scale. Managing thousands of RU\/s settings becomes difficult, and provisioning dedicated capacity for every tenant can be costly\u2014especially when many tenants are inactive. Monitoring performance and usage across thousands of accounts also adds to the overhead.<\/p>\n

Azure Cosmos DB fleets introduce two key capabilities\u2014pools<\/strong> and fleet analytics and monitoring<\/strong>\u2014to simplify capacity management and provide at-scale visibility across your tenant environments.<\/p>\n

 <\/p>\n

\"Fleet<\/a><\/p>\n

Pools<\/strong><\/h3>\n

Fleets let you organize the database accounts in your multi-tenant application into sub-groups called fleetspaces<\/strong>.<\/p>\n

Within each fleetspace, you can create an optional throughput pool (RU\/s)<\/strong> that all accounts in the group can share.<\/p>\n

Each resource still gets dedicated RU\/s that are guaranteed and always available to that resource. When a resource needs more than its dedicated RU\/s\u2014such as during a traffic spike\u2014it can draw from the shared pool. This approach allows you to provision each tenant based on typical usage instead of over-provisioning for peak load, significantly simplifying capacity management. You maintain the performance and security isolation benefits of separate database accounts per tenant while optimizing for cost by using the pool.<\/p>\n

In the below example, we\u2019ve set up a fleetspace with 10 database accounts and a pool of RU\/s. Each database account has 1 container with dedicated autoscale 100-1000 RU\/s. We see that for spikes beyond 1000 RU\/s, which otherwise would have been rate-limited, the requests are now served by the pool.<\/p>\n

\"FleetAccounts<\/a><\/p>\n

\"RU\/s<\/a><\/p>\n

Pool RU\/s autoscale by default. You can configure custom minimum and maximum limits with up to a 10x scaling range. Billing is based on the highest RU\/s the pool reaches within each hour.<\/p>\n

Learn more: https:\/\/aka.ms\/CosmosDBFleetPools<\/a><\/p>\n

Fleet analytics \/ monitoring<\/strong><\/h3>\n

Fleets include built-in monitoring tools that give you visibility across all your database accounts at scale. With the new At-scale Azure Monitor view<\/strong>, you can track performance, traffic, and usage across your entire fleet. Use this view to quickly identify specific accounts or tenants experiencing issues, and drill in for deeper analysis.<\/p>\n

\"Azure<\/a><\/p>\n

You can also enable optional fleet analytics<\/strong> to collect hourly data on cost, performance, and usage. This data streams to a Microsoft Fabric workspace or an Azure Storage account, making it easy to perform long-term trend analysis. Use the built-in visualizations or run custom queries to answer key questions such as:<\/p>\n