DIWe're using Prisma for all our projects, and we haven't looked back a single time. Thank you for your feedback!Reply·Article·Jan 24, 2022·Migrating a Large Production App From TypeORM To Prisma
DII'm really glad it helped! Thank you for your feedback!Reply·Article·Sep 21, 2021·Migrating a Large Production App From TypeORM To Prisma
DIHi, We have a non-breaking migrations policy and we migrate with a custom script to keep schemas in sync.Reply·Article·Aug 13, 2021·Schema-Based Multi-Tenancy with NestJS and Prisma
DIHello, 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.Reply·Article·Apr 12, 2021·Schema-Based Multi-Tenancy with NestJS and Prisma
DIHi 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.Reply·Article·Dec 22, 2020·Schema-Based Multi-Tenancy with NestJS and Prisma