|
|
|
|
|
|
by gwen-shapira
975 days ago
|
|
|
We don't have per-tenant schema right now, but we have started designing multi-version experience and it doesn't seem too far from here. Nile is different from DB per tenant in a single PG cluster in that it is much lower overhead per tenant. Since we offer a service, it will translate to lower cost. The DB-per-tenant gets painful after the first few 100 tenants, but some SaaS have thousands of tenants, each with very low activity. Our model makes inactive tenants nearly free. In addition, we also provide the "unified view", which lets you query all your tenants as if they were in the same DB. So you can connect as an admin and "select * from my_table" will give you the results for all tenants. Can be pretty handy. |
|
|
What are you thinking will happen when a SaaS grows like Salesforce, with a very large number of tenants, where some of the tenants have very large databases? What will Nile do when the database just can't fit in a single Postgres cluster?
Edit: Never mind, I see from your web site that moving tenants between databases is one of the main things you try to address.