Data design for partitioned databases
Design an application's data to drive faster performance, lower cost, and future scalability.
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