Skip to main content
Tech Stack progress
intermediatePage 1 of 27

5. The 2026 Tech Stack — Overview

Every major tool in the 2026 web stack, organized by layer. Skim once; refer back when choosing.

Part 5: The 2026 Tech Stack Decoded

Every major tool in modern web development — what it does, when to use it, why it exists.

New to web dev? How to read this chapter

Don't read front-to-back yet. Finish Roadmap Stages 5–8 (TypeScript, React, Next.js) first, then return here to decode the tools you're using. Skim Advanced companion pages (01b, 02b, etc.) only when the on-ramp page points you there.

Absolute-beginner orientation

Why this chapter looks overwhelming: It is overwhelming — there are hundreds of tools in modern web development, and this chapter catalogs the important ones. Don't read it front-to-back like a novel. Skim once to know what exists, then come back to specific sections when you need to make a decision.

The "stack" mental model: A web application is built in layers. Each layer has its own tools:

  • Language layer — what you write code in (TypeScript, Python, Go...)
  • Framework layer — the scaffolding (Next.js, Django, Rails...)
  • Styling layer — how it looks (Tailwind, CSS Modules...)
  • Data layer — where information is stored (Postgres, MongoDB, Redis...)
  • Auth layer — who can do what (Clerk, Auth0, custom JWT...)
  • Hosting layer — where it runs (Vercel, AWS, Cloudflare...)
  • Observability layer — how you know it's working (Sentry, Datadog...)

A "stack" is just one specific choice for each layer. The famous acronyms (MERN, LAMP, T3) are all just specific stack combinations.

If you only remember one thing: You don't need to know every tool. You need to know one tool per layer well enough to ship a working app, then expand from there.

For a new full-stack project, the boring-but-effective combination:

LayerRecommendation
LanguageTypeScript
FrameworkNext.js (or Astro for content)
StylingTailwind + shadcn/ui
DatabasePostgres (Supabase or Neon)
ORMDrizzle
AuthClerk or Better Auth
HostingVercel or Cloudflare
ObservabilitySentry + PostHog + Better Stack
AIVercel AI SDK + Anthropic/OpenAI

This is the "boring" path. It's boring because it works. Save creativity for your product.

Pages in this chapter

  1. Languages — TypeScript, Python, Go, Rust, Java/Kotlin, C#, PHP, Ruby.
  2. Frontend Frameworks — React, Vue, Svelte, Solid, Astro.
  3. Styling — Tailwind, shadcn/ui, CSS Modules, alternatives.
  4. Build Tools — Vite, Turbopack, Bun, esbuild.
  5. Package Managers — pnpm, Bun, npm, Yarn.
  6. State Management — TanStack Query, Zustand, forms.
  7. Forms & Server Actions — RHF + Zod, server actions, optimistic updates.
  8. Design Systems & Storybook — tokens, accessible components, visual-regression.
  9. Backend Frameworks — Hono, Express, Fastify, NestJS, FastAPI, Django, more.
  10. APIs — REST, tRPC, GraphQL, gRPC, WebSockets, SSE, webhooks.
  11. Databases — Postgres, SQLite, MongoDB, Redis, search, vector.
  12. ORMs & Database Tools — Drizzle, Prisma, Kysely, raw SQL.
  13. Authentication — Clerk, Better Auth, Auth.js, Auth0, Supabase.
  14. Background Jobs — Trigger.dev, Inngest, BullMQ, others.
  15. Services — Payments, email, files, video, maps, notifications.
  16. AI Infrastructure — Models, SDKs, embeddings, observability.
  17. Hosting Platforms — Edge, App, Cloud.
  18. DevOps & Infrastructure — Containers, K8s, IaC, secrets.
  19. Monitoring & Observability — Errors, logs, metrics, traces.
  20. Code Quality & Dev Tools — Biome, ESLint, hooks.
  21. Editors & AI Assistants — VS Code, Cursor, Claude Code.

When you finish, move on to Chapter 6: Cloud Platforms — the infrastructure your stack actually runs on.