Details
-
Question
-
Resolution: Done
-
Blocker - P1
-
None
-
2.0.1
-
Ubuntu (latest)
Description
Hi,
I have an application that is virtually partitioned on a relational database (MySQL) and we are moving to Mongo. We have 20,000 accounts (with an accountid) partition field. I have a question surrounding our design approach with moving to Mongo.
We currently hoped to give each account it's own database and then have a central account manager db to control routing. This appears to be working really well and performance is awesome.
We could not find any limit anywhere on DB numbers per installation. There was a reference to the file access limits (which we increased to 65536 on our ubuntu installation)
Should we collapse all accounts into a single DB, using an account key field, apply combined indexes etc and then rely on auto-sharding? Or is it ok to continue to create new databases per account to reduce the index overheads for large accounts?
Your help is much appreciated