Data design for partitioned databases

March 24, 2019 devadvin

Choosing a partition key in a partitioned database on the cloud is an important decision to make, and you need to make it before any data is added to the database.

Also, keep in mind that the design of an application’s data is key to faster performance, lower cost, and future scalability.

An e-commerce example of a online shopping portal is a good way to look at how you can design data and devise indexes to service the application’s access patterns. You can see examples of separate databases for users, products, and order.

Follow the examples at Partitioned Databases – Data Design, part 2 in a Cloudant blog series and try them out with Cloudant as part of IBM Cloud for free.

You can learn more about data indexing in the Cloudant documentation

Previous Article
Migrating to partitioned databases
Migrating to partitioned databases

Copy over data while modifying each document's key field on the way.

Next Article
Keep sensitive data safe and withstand the rigors of natural disasters
Keep sensitive data safe and withstand the rigors of natural disasters

It’s not enough to respond to a natural disaster; healthcare facilities need to be prepared before disaster...

×

Want our latest news? Subscribe to our blog!

Last Name
First Name
Thank you!
Error - something went wrong!