Prisma in Production Discussion Panel
summary
Panelists report that Prisma delivers type safety everywhere and a single schema that keeps migrations and DB models in sync, cutting runtime errors and shortening time-to-MVP. Teams pair Prisma with GraphQL federation with Apollo Gateway, Nexus or Nest, use DataLoader batching and multi-layer caching for performance, and rely on Prisma Studio for inspection. Prisma Migrate is generally workable though legacy versions required care, and teams still drop to raw SQL for analytics.
AI-written summary · about
chapters (15)
- 0:00Introduction and panelists
- 3:42Fun yes or no questions
- 6:11Highest priorities in projects
- 8:51Tech industry trends
- 11:37Problems Prisma solved
- 15:04Role of caching in architecture
- 18:37Building GraphQL APIs with Prisma
- 24:00Choosing Prisma technology
- 29:16Prisma roadmap excitement
- 31:13Challenges with multiple databases
- 33:31Microservices communication
- 36:36Security in growing applications
- 38:49Database lessons learned
- 40:47Raw SQL vs Prisma
- 41:13Closing remarks and Q&A
related talks
31mUnderstanding GraphQL, databases and Prisma
29mModernize and Robust Applications with Prisma & Azure SQL Server
28mNext.js and Prisma: Databases in Serverless Made Easy
18mPrisma io Data Magic in Next Server Components
46mBoost your API Development with GraphQL & Prisma
16mHow Next.js and Prisma make frontend developers full-stack
20mPrisma & Expo: A Better Path to Local-First Apps
17mDatabase as Code with PlanetScale and Prisma