Jamstack Makes Front-end Full Stack
Thom Krupa, co-founder of Bejamas, on building dynamic apps on the Jamstack
This shift matters because modern web tools moved a big chunk of backend work from writing and operating servers to wiring together managed services. A front end developer can now build the screen, call an auth service, read and write to a hosted database, and deploy server side logic through the same framework and hosting workflow. That speeds up small teams, but it also changes what platform vendors are really selling, which is a simpler path to shipping full web apps.
-
In practice, this means a React developer can build a product page, user login, form handling, search, and payments by connecting APIs and serverless functions instead of standing up custom app servers. The job expands from styling pages to assembling working software from hosted building blocks.
-
The platforms winning here, like Vercel and Netlify, are packaging CDN, compute, routing, and functions behind a low friction workflow. The value is less the raw infrastructure and more the fact that a developer can push code and get a production app without touching cloud consoles and provisioning settings.
-
The boundary still shows up in highly dynamic products. At PayPal and Amazon, teams could separate front ends from APIs and ship faster, but heavily personalized pages often led to more client side loading and performance issues, which pushed teams toward hybrid models like Next.js with both front end and server rendering in one setup.
The next step is not front end replacing backend, but front end absorbing more of the default web app stack. As edge functions, hosted databases, and hybrid frameworks improve, more product work will start with one developer owning the whole user facing application, while specialized backend engineers concentrate on the hard parts, custom systems, data models, and infrastructure at scale.