O'Reilly logo

Learning Azure DocumentDB by Riccardo Becker

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

Partitioning data

As we saw in Chapter 1, Getting Started with DocumentDB, DocumentDB has limits on its resources. A maximum of 10 GB per collection and maximum requests units per collection is set to 2,500 per second. To be able to go above these limits and reach a truly high scale, we need to partition our data by using sharding. For more information on the sharding pattern, please visit https://msdn.microsoft.com/en-us/library/dn589797.aspx.

Collections in DocumentDB are both logical and physical containers. Triggers and stored procedures do not go beyond these boundaries when it comes to transactions.

This section will discuss how to use sharding. The best sharding techniques are based on how our data is formatted and accessed. Basically, there ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required