---
title: "Comment by Jonathan Mitnik on \"Schema-Based Multi-Tenancy with NestJS and Prisma\" | Hashnode"
description: "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"
url: "https://hashnode.com/posts/schema-based-multi-tenancy-with-nestjs-and-prisma/5fe1c2b1a669d865551f6756/comment/5fe1d42faaa31068bc22b430"
---

[Discussion](https://hashnode.com/posts/schema-based-multi-tenancy-with-nestjs-and-prisma/5fe1c2b1a669d865551f6756)

Comment [Schema-Based Multi-Tenancy with NestJS and Prisma](https://hashnode.com/posts/schema-based-multi-tenancy-with-nestjs-and-prisma/5fe1c2b1a669d865551f6756)

[Jonathan Mitnik](https://hashnode.com/@Jonik)

[Dec 22, 2020](https://hashnode.com/posts/schema-based-multi-tenancy-with-nestjs-and-prisma/5fe1c2b1a669d865551f6756/comment/5fe1d42faaa31068bc22b430)

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?

[Dario Ielardi](https://hashnode.com/@darioielardi)

[Dec 22, 2020](https://hashnode.com/posts/schema-based-multi-tenancy-with-nestjs-and-prisma/5fe1c2b1a669d865551f6756/comment/5fe1d42faaa31068bc22b430#reply-5fe1e1fe2d84df6a9bc97c38)

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.

[Jonathan Mitnik](https://hashnode.com/@Jonik)

[Dec 22, 2020](https://hashnode.com/posts/schema-based-multi-tenancy-with-nestjs-and-prisma/5fe1c2b1a669d865551f6756/comment/5fe1d42faaa31068bc22b430#reply-5fe1e255227cbd6ac0517717)

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!
