In which cases is Next.js overkill?

Next.js is a powerful tool, but it's not always justified. There are scenarios where its capabilities are either unused or create unnecessary complexity.

---

#When Next.js is truly overkill

#1. A simple SPA without SEO

If this is:

• an internal admin panel
• a dashboard
• a CRM
• an analytics panel

SEO isn't needed, SSR/SSG bring no benefit. Vite + React will be simpler, faster, and cheaper.

---

#2. A purely client-side application

• everything runs in the browser
• data comes only via an API
• there's no server-side logic
• there are no content pages

In this case, Next.js:

• adds a server
• complicates deployment
• provides minimal benefits

---

#3. A small project / an MVP for "a couple of screens"

When:

• 2-5 pages
• simple logic
• a fast launch matters more than architecture

Next.js can be heavier than needed:

• more concepts
• more magic
• a higher entry threshold

---

#4. A complex backend already exists

If you have:

• a large backend (Nest / Spring / microservices)
• a strict backend architecture
• no need for a BFF

Next.js is better used only as the frontend, and sometimes replaced with an SPA entirely.

---

#5. No experience with server-side rendering

For a team with:

• junior developers
• no understanding of SSR / hydration / cache
• no DevOps resources

Next.js can lead to:

• strange bugs
• caching problems
• "magic" that nobody understands

---

#In short: when NOT to take Next.js

• admin panels
• simple SPAs
• applications without SEO
• small projects without growth
• teams without SSR experience

---

#When Next.js is 100% justified

• SEO matters
• content pages
• a public website / SaaS
• speed and scale are needed
• frontend + server in one place

---

#Interview answer

Next.js is overkill for simple SPAs, admin panels, and applications without SEO, where server-side rendering and static generation aren't used, and its capabilities only complicate the architecture.