Thanks for your reply Justin,
I'd like to avoid having multiple tenants in the same database, I feel
multi-database is easier to scale, and simpler in a code maintenance
sense. It does required to run database migrations once per tenant,
but I still see it as the better solution.
One solution I
Have you looked at the Sites framework? You could have multiple
tenants using one database and use a ForeingKey to a Site object to
structure the data. This will result in more complex queries, but
might be less of a cost than the maintenance issues (see below).
If you continue reading that IBM
Hey,
I'm wondering if Multi-DB supports some kind of multi-tenancy on the
DB level (one app instance supporting multiple databases - one per
client - 2 on
http://www.ibm.com/developerworks/cloud/library/cl-multitenantsaas/figure0.gif).
I don't think it does, but just want to be sure.
I'm
3 matches
Mail list logo