Account level throughput

Instead of defining throughput per each collection, sometimes you would like to set a fixed value for the whole account. This is a great addition if you have many different containers and instead of paying for each individually (as you remember—it was over $20 per month), you can go to Account level throughput and set a throughput for the whole account:

The only limitation of this feature is you can no tables currently in the account. If you enable it, all your requests to all tables will share the same amount of throughput (so you can pay less, but in the case of "greedy" collections you can run out of RUs). The downside ...

Get Hands-On Azure for Developers now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.