Most WCH services currently store 1 tenant per Cloudant database this has resulted in WCH not following Cloudant best practices and resulted in a very high database count for the WCH solution. This puts the entire solution at risk as we grow our number of tenants and tenant activity grows. To work around this limitation in regards to replication we are in process of deploying the Kafka replication but this limits growth in each cluster further as it drives the number of writes higher.

* Moving to one database for each service would allow us to fit a far greater number of tenants in a single database.
* Moving to this type of solution may eliminate the need for Kafka replication and allow us to leverage the database replication removing a fair amount of processing from our solution.
* It will allow us to greatly reduce the databases for the solution from 1 per tenant to 1 per service.
* The solution will allow us to keep costs per tenants lower, increasing revenue.

In addition, other solutions offered by the foundation and platform teams like CouchBase allow 1 database per solution. This could align us better with that type of solution in case we are forced to move there in the future.

This is a proof other services could be expected to follow this conversion once proven.