Suggest an editImprove this articleRefine the answer for “Why is Next.js considered a fullstack framework?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)**Next.js** is considered a **fullstack framework** because within one project it combines **frontend + backend + server-side rendering**, without needing to run a separate server. **Key point:** Next.js is considered a fullstack framework because it lets you implement the UI, server-side rendering, an API, and database work in a single project, without a separate backend application.Shown above the full answer for quick recall.Answer (EN)Image**Next.js** is considered a **fullstack framework** because within one project it combines **frontend + backend + server-side rendering**, without needing to run a separate server. --- ## What makes Next.js fullstack ### 1. Server code next to the UI In Next.js you can write code that: - runs **only on the server** - has access to the DB, secrets, the file system - never reaches the browser Example: - Server Components - Server Actions This is already **backend logic**, not just frontend. --- ### 2. API Routes (built-in backend) Next.js lets you create API endpoints right in the project: - REST / RPC - form handling - auth - webhooks - integrations with third-party services Without Express / Nest / Fastify. --- ### 3. Working with the database directly On the server side of Next.js you can: - connect to a DB (PostgreSQL, MySQL, etc.) - run ORM/SQL queries - validate data UI -> Server Action -> DB Without a separate backend application. --- ### 4. Managing data on the server Next.js takes care of: - SSR / SSG / ISR - data caching - revalidate - streaming That is, **the server manages the data**, not the browser. --- ### 5. Authorization and security In Next.js you can: - read cookies / headers - check sessions - hide business logic - work with tokens These are typical backend tasks. --- ### 6. A single project architecture In one repository: - UI (React) - routes - server logic - API - rendering - optimization Less infrastructure Less syncing Faster development --- ## What is important to understand (a common trap) Next.js is **not a replacement for a complex backend**. - complex domain services - heavy background jobs - complex queues - microservices For that, it's better to have: - Next.js - frontend + BFF - a separate backend (Nest.js, Spring, etc.) --- ## Short answer for an interview > **Next.js is considered a fullstack framework because it lets you implement the UI, server-side rendering, an API, and database work in a single project, without a separate backend application.**For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.