Discussion on "Schema-Based Multi-Tenancy with NestJS and Prisma"

Dario Ielardi · 2020-12-22T09:56:01.442Z

We recently migrated a big NestJS project to adopt Prisma as the ORM. It turned out to be a great decision, and I described our wonderful experience in a recent blog post. The project is an API backend for a multi-tenant system, where each tenant has...

Dario Ielardi Thank you very much for this article. I have a project to develop that respects this architecture. I would like to know if the tenant databases must be created manually? if I have a frontent with angular for example, how to identify a tenant when creating an account from the front for example and save it in the right database?. A code example would help me more. Thanks in advance

Do you have any tips on how to manage migrations on multi-tenant schema

This is wonderfull!!!

Hi, I'm curious. Since you have a database per tenant, how do you make sure all those databases share the same structure and get all the latest migrations?

Hi, We have a non-breaking migrations policy and we migrate with a custom script to keep schemas in sync.

Dario Ielardi Could you give a brief example of how to synchronize tenants' databases synced?

Dario Ielardi How you synchronize the shemas? How you run your migrations?

Very neat solution, congrats; I just want to point out a little detail (and please correct me if I'm wrong), you don't need to explicitly make prismaClientProvider request-scpoed, since you are injecting REQUEST into it, wich is in itself a request-scpoed provider, then his scope is bubbled up by the injection chain.

Hello, thank you for your kind words.

You're right, there's no need to explicitly make the custom provider request-scoped, I did that just to be totally explicit about the intended behavior.

Hi Dario,

thanks for the excellent write-up!

I was wondering, what alternative would you consider if you do have potentially thousands of tenants? I suppose you would then simply have to create the prisma connections based on incoming request?

Hi Jonathan, thanks for your kind words!

In a situation where the number of tenants is so big I'd probably avoid a schema-based architecture, and rather go with row-level data separation. That way I'd only need one database connection for one Prisma client.

Ah cool, indeed that's what we are currently "confined" to so to speak as well, nothing to do about it I suppose :). Thanks for your input on it!

Search Hashnode

Schema-Based Multi-Tenancy with NestJS and Prisma

Responses6