Database Integration — Complete Guide
Database Integration — Complete Guide: free step-by-step lesson with examples, common mistakes, and interview tips — part of Next.js Tutorial on Toolliyo Academy.
On this page
Next.js Tutorial (LearnHub) · Lesson 23 of 100
Database Integration
Beginner ✓ → Intermediate → Advanced → Professional
Intermediate · 2 — Building apps · ~14 min read · Module 3: Data & Forms
Introduction
You know the basics now. Here we use Database Integration in real LearnHub screens — layouts, data, and APIs. Still plain language, just a bit more depth. Connect LearnHub to PostgreSQL, MySQL, or MongoDB via Prisma, Drizzle, or the native driver. Server Components and Server Actions run DB queries on the server only. Courses, users, and progress must persist. Files and in-memory arrays reset on deploy — a real database is required for production LearnHub.
Data and forms power course lists, enrollments, and progress. Learn these patterns slowly — test in a small page first.
When will you use this?
Reach for data fetching and Server Actions when pages need database content or form submissions.
- Enrollments, quiz scores, and course progress load from the server — often with Server Actions.
- Forms that enroll a student in a course use Server Actions instead of a separate REST call.
Real-world: Zoho-style SaaS dashboard
The B2B SaaS team building Zoho-style SaaS dashboard uses Database Integration to persist courses, users, and enrollments in PostgreSQL or MongoDB. tenant admins never see the TypeScript files — they just get a fast, reliable billing, team settings, and analytics widgets.
Production-style code
// lib/db.ts — concept with Prisma (install in later lesson)
import { PrismaClient } from '@prisma/client';
const globalForPrisma = globalThis as unknown as { prisma: PrismaClient };
export const prisma = globalForPrisma.prisma ?? new PrismaClient();
if (process.env.NODE_ENV !== 'production') globalForPrisma.prisma = prisma;
// app/courses/page.tsx
export default async function CoursesPage() {
const courses = await prisma.course.findMany({ orderBy: { title: 'asc' } });
return <pre>{JSON.stringify(courses, null, 2)}</pre>;
}
What happens in production: In Zoho-style SaaS dashboard, getting Database Integration right means tenant admins trust the billing, team settings, and analytics widgets every day.
Lesson example (start here)
Copy this smaller example first. Once it works, compare it with the real-world code above.
// lib/db.ts — concept with Prisma (install in later lesson)
import { PrismaClient } from '@prisma/client';
const globalForPrisma = globalThis as unknown as { prisma: PrismaClient };
export const prisma = globalForPrisma.prisma ?? new PrismaClient();
if (process.env.NODE_ENV !== 'production') globalForPrisma.prisma = prisma;
// app/courses/page.tsx
export default async function CoursesPage() {
const courses = await prisma.course.findMany({ orderBy: { title: 'asc' } });
return <pre>{JSON.stringify(courses, null, 2)}</pre>;
}
Line-by-line walkthrough
| Code | What it means |
|---|---|
// lib/db.ts — concept with Prisma (install in later lesson) | Comment — notes for humans; the compiler ignores it. |
import { PrismaClient } from '@prisma/client'; | Imports a module so you can use its exports in this file. |
const globalForPrisma = globalThis as unknown as { prisma: PrismaClient }; | Part of the Database Integration example — read it together with the lines before and after. |
export const prisma = globalForPrisma.prisma ?? new PrismaClient(); | Part of the Database Integration example — read it together with the lines before and after. |
if (process.env.NODE_ENV !== 'production') globalForPrisma.prisma = prisma; | Part of the Database Integration example — read it together with the lines before and after. |
// app/courses/page.tsx | Comment — notes for humans; the compiler ignores it. |
export default async function CoursesPage() { | Default export — the main page or component this file provides to Next.js. |
const courses = await prisma.course.findMany({ orderBy: { title: 'asc' } }); | Part of the Database Integration example — read it together with the lines before and after. |
return <pre>{JSON.stringify(courses, null, 2)}</pre>; | Returns JSX — what the user sees in the browser. |
} | Closes a block started by { above. |
How it works (big picture)
- Singleton Prisma client avoids connection storms in dev hot reload.
- findMany runs SQL on the server.
- Never import prisma in Client Components.
Do this on your computer
- Choose PostgreSQL locally or hosted (Neon, Supabase)
- Plan tables: User, Course, Enrollment, LessonProgress
- Sketch Prisma schema on paper
- Wire DATABASE_URL in .env.local
- Read the real-world section and name which part of LearnHub uses this topic.
- Run the example locally with npm run dev and confirm the same behavior.
- Change one value in the example (route, text, or course id) and predict what will happen before you save.
Experiments — try changing this
- Change a string or route in the example and save — watch the browser update.
- Break the code on purpose (remove a bracket), read the error overlay, then fix it.
- Change the API URL or course id and see how the page data changes.
- Use npm run dev while editing Database Integration — the page hot-reloads on save.
Remember
DB access stays server-side. ORM helpers like Prisma are common. Use env DATABASE_URL for connection string.
Common questions
SQLite for learning?
Fine locally; use PostgreSQL before deploy to Vercel serverless.
How long should I spend on Database Integration?
Until you can explain it in your own words and run the example without looking at the answer. Beginners often need 30–60 minutes per new concept; setup lessons may take one afternoon.
What if I get stuck on Database Integration?
Re-read the line-by-line walkthrough, check the terminal and browser overlay for errors, and compare your code character-by-character with the example. Search the exact error text — someone else had it too.
Where is Database Integration used in real jobs?
See the real-world section above — the same pattern appears in LMS, e-commerce, SaaS, and dashboards. Interviewers ask you to explain it using one concrete example.