At our expected rate of growth, we are pushing the boundaries of what a single Cloudant cluster can support. Our current database count is as 28,500 dbs in the WDC cloudant cluster and 13,500 dbs in the FRA Cloudant cluster. Adding 2,100 WCA tenants will drive the database count up by approximately 40,000 additional databases.

The goal is to keep the database count below 40,000 as we have seen issues related to performance at 35,000 and more databases.

We can segment our tenants into sets of tenants limiting each set to between 10 and 12.5k databases. Each set of tenants is stored in its own 'Cloudant Account' on our current cluster. There is no cost associated with this segmentation and the account creation is free and easy. This provides us with multiple options:

* Sets of users can readily be moved to new Cloudant clusters if and when necessary.
* Sets of users, trials, for example, can be throttled giving priority to paying tenants throughput and performance.

This change affords us options once we hit this performance wall. Options with a recovery time of 24 hours or less while the alternative reactive approach could take as long as a week to really recover as we'd me manually shifting and or removing selected tenants.

We should aim to do this prior to hitting 40k dbs and prior to adding the WCA tenants.