{"id":1130,"date":"2020-05-19T10:36:38","date_gmt":"2020-05-19T17:36:38","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/cosmosdb\/?p=1130"},"modified":"2020-08-19T09:32:29","modified_gmt":"2020-08-19T16:32:29","slug":"autoscale-serverless-offers","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cosmosdb\/autoscale-serverless-offers\/","title":{"rendered":"Autoscale + serverless: new offers to fit any workload"},"content":{"rendered":"

This blog post was co-authored by Deborah Chen and Thomas Weiss, program managers on Azure Cosmos DB.\u00a0<\/em><\/p>\n

Update<\/em><\/strong>: Serverless is available in preview<\/a> for the Core (SQL) API as of August 19, 2020.<\/p>\n

Over the years, we\u2019ve heard from many of you that you\u2019d like more flexibility with the Azure Cosmos DB billing model to better balance cost and performance. With our current provisioned throughput model, it\u2019s easy to set the exact throughput you need for your workload, measured in Request Units per second (RU\/s), guaranteed by Azure Cosmos DB\u2019s SLAs. For scenarios where your application doesn\u2019t need constant throughput however, we know choosing the right RU\/s can be a challenge. For example, some apps might have variable, unpredictable traffic, while others might not have consistent usage at all, seeing only sporadic spikes of usage.<\/p>\n

To make this easier, we\u2019re excited to announce two new ways to pay for your database operations: the general availability of autoscale provisioned throughput<\/strong>, which brings automatic scaling to our provisioned throughput model, and the upcoming preview of serverless<\/strong>. Together, provisioned throughput and serverless ensure that Azure Cosmos DB is, more than ever, a database that delivers the best performance and cost-effectiveness for any kind of workload.<\/p>\n

Autoscale provisioned throughput (GA)<\/h2>\n

With autoscale provisioned throughput (formerly known as \u201cautopilot\u201d) Azure Cosmos DB automatically and instantaneously scales your throughput (RU\/s) based on the workload usage within a preset range. This means you can focus on building your application and let Azure Cosmos DB handle the work of capacity and scale management for you. Autoscale is well suited for mission-critical applications that have variable or unpredictable traffic patterns.<\/p>\n

It\u2019s backed by all Azure Cosmos DB SLAs, supports all Azure Cosmos DB APIs \u2013 Core (SQL), Gremlin, Cassandra, Table, and API For MongoDB \u2013\u00a0 and helps optimize your RU\/s usage and cost by scaling down when not in use.<\/p>\n

How does autoscale work?<\/h3>\n

You set the highest or maximum throughput (RU\/s), T_max, you want your database or container to scale to. Azure Cosmos DB scales the RU\/s based on usage, so that it\u2019s always between 10% of T_max and T_max. For example, if you set a maximum throughput of 10,000 RU\/s, this will scale between 1000 to 10,000 RU\/s. Billing is done on a per-hour basis, for the highest RU\/s the system scaled to within the hour.<\/p>\n

\"Autoscale<\/p>\n

Based on your feedback from the preview, with GA, we are introducing several new features to make autoscale easier to use:<\/p>\n

Custom values are now supported for the maximum throughput (RU\/s),<\/strong> which replaces the set of values available in the preview. This gives you more flexibility to set the right value based on the needs of your workload. Any resources created during the preview will automatically be compatible<\/a> with the new model.<\/p>\n

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

Autoscale can now be enabled on existing databases and containers.<\/strong> This makes it easy to take advantage of autoscale without having to migrate your data or create resources. If you have an existing workload with a variable or unpredictable traffic pattern, and don\u2019t currently do manual scaling yourself, enabling autoscale can help optimize your RU\/s usage and cost, as it will scale down to the minimum of the RU\/s range when not in use.<\/p>\n

Finally, we now have programmatic support<\/strong> in the latest versions of the Azure Cosmos DB SDKs for .NET and Java, Resource Manager, and commands for Cassandra API and API for MongoDB. Support for PowerShell and Azure CLI will be available in an upcoming release.<\/p>\n

How you can save with autoscale provisioned throughput<\/h3>\n

Imagine a workload with certain characteristics:<\/p>\n