1000 databases and 3 collection per database

[Joao_Pinela]

Hello Steve,

Thanks . That might be a good fit for this question…

Any case where "Collection per entity" is a good model?

Hello Asya, thank you for your feedback one good idea, I would think, is data isolation/ privacy . That is really the only reason, because other than that, you can “split” in one single collection by a simple attribute “house_id” or similar. I don’t see any more benefits. Performance-wise, versus the complexity of coding, doesn’t seem one. Would it be THAT much better, if there isn’t a requirement for data isolation for privacy? Thank you again. Best Regards, JP

And regarding this issue, it is even worse. Thousands of databases with 3 collections per database (the same ones) with a few records.

For the same app (so data isolation / privacy is not a concern). I know in my soul this makes no sense.

A single collection with an attribute “city_id” (or similar) , I would say would be sufficient.
Do you see something else?

Thank you again.
Best Regards,
JP