Front-end vs Back-end: A Definition That Keeps Shifting

In 2014, I answered a question on Stack Overflow in Portuguese asking what front-end and back-end actually mean. It scored 4 upvotes. The answer seemed obvious: front-end is what the user sees, back-end is what runs on the server. Easy.

Eleven years later, the boundary has moved so much that the question deserves a fresh answer.

The 2014 Definition: Clear Division

Front-end: HTML, CSS, JavaScript running in the browser. Technologies: HTML, CSS, jQuery. Responsible for presentation, layout, and interactivity.

Back-end: Code running on the server. Technologies: PHP, Java, Python. Responsible for business logic, databases, and generating the HTML sent to the browser.

The division was physical: front-end code ran on the client machine, back-end code ran on the server. You needed two different skillsets. “Full-stack” was still a stretch goal.

The 2026 Reality: Blurred Lines

React Server Components

React 18+ lets you write components that run on the server and stream HTML to the client. Same language (JavaScript), same component model, but the code runs on the server:

// This component runs on the SERVER (never sent to the browser)
async function UserProfile({ id }) {
  const user = await db.user.findUnique({ where: { id } }); // Direct DB access
  return <div>{user.name}</div>;
}

Is this front-end or back-end? It’s a React component (front-end) that queries a database (back-end). The answer stopped being useful.

Edge Functions

Cloudflare Workers, Vercel Edge Functions, and Deno Deploy run JavaScript at CDN edge nodes — geographically distributed, milliseconds from every user. They’re “backend” (server-side code) but deployed like “frontend” (the same pipeline that deploys your website).

Astro, Next.js, Remix

These frameworks generate HTML on the server but hydrate interactivity in the browser. One file can contain server-side data fetching code and client-side event handlers. The framework decides what runs where.

What Still Holds

The concepts haven’t vanished — they evolved:

Concept	2014	2026
Where code runs	Strictly client or server	Determined by framework/runtime
Skills needed	Separate front/back specialists	Full-stack common, but depth still matters
Database access	Server only	Also from server components, edge
State management	Server: session/DB, Client: JS vars	Same, plus server state streaming

Key Takeaway

In 2014, front-end vs back-end described where code ran. In 2026, it more often describes what the code does — presentation and interaction vs business logic and data access. The “where” became a framework concern. Understanding both sides still matters; the line between them just got blurrier.