-
Notifications
You must be signed in to change notification settings - Fork 45
Support sharded multi-tenant database model #31
Comments
Hi, thank you for the compliment 🙂 The initial purpose of this project is to be a wrapper of Prisma to handle the multi-tenant design pattern. I like the fact that For what I understand, supporting the sharded multi-tenant pattern would require to have complete control over the schema of the project using I'm not against such evolution, however, I'll probably not do it in the near future, as that would require a lot of work. However, if you have an idea on how I could implement this pattern in a way that would:
|
I agree with you that It will lead to more complexity and currently I'm not looking for that solution but maybe a "nice to have" in the future since the pattern has some advantages. However database-per-tenant model will be the best approach for most applications. Anyway, it's preferable to wait for a stable Prisma 2 and then think about it. In the mean time, we can leave this issue open.. |
Hey @fabiofdsantos, good news! 🥳 Prisma now has a Middleware feature, that would allow for the However, I'll first need to implement the "one DB for all tenants" model (see issue). Then, I'll be able to make a mix of those two and support the Sharded model 🙂 |
Great news! I no longer use Prisma but I expect to come back in a few months |
Hey @Errorname is there any progress on this model? |
First of all, thanks for this amazing work!
Since this project is using "database per tenant" as tenancy model, are you considering to support the shared multi-tenant model in the future?
More details:
https://github.com/microsoft/WingtipTicketsSaaS-MultiTenantDB#sharded-multi-tenant-saas-pattern
The text was updated successfully, but these errors were encountered: