#Django multi tenant implementations

3 messages · Page 1 of 1 (latest)

hardy talon
#

Hi everyone,

anyone here using either django-multitenant or django-tenants and has experience in rolling those out on production apps?
We currently have a shared-db & shared-schema approach, which is sometimes cumbersome (and error prone) to deal with, so I'm looking into using a library to use this.
The separate schemas look a bit daunting / like a heavy change. Any experiences with that? (Especially regarding the migration and "future-proofness")

solemn spade
#

I'm in the same boat as you

hardy talon
#

https://github.com/bernardopires/django-tenant-schemas/issues/387
Found some indication in that issue (and others), that hint at the fact that DTS seems to not like >100 tenants, which is actually not an option for us. I'm a bit confused on why it's that slow, but yeah.

Postgres row-level security also seems to be a thing, bearing performance overhead as well, though (not as critical for us in general, though).

Might continue with the FK-to-tenant approach :/ Hoped for something better

GitHub

We are using django-tenant-schemas in production with more than 1500 tenants and migrating is painfull, we are addressing the problem from diferents sides: trying to reduce the number of tenants to...