CDN-First Jamstack for Dynamic Apps
Thom Krupa, co-founder of Bejamas, on building dynamic apps on the Jamstack
The real shift is that Jamstack stopped meaning fully static pages and started meaning CDN first delivery with compute moved out to many small endpoints instead of one always on web server. That lets a team prebuild what can be prebuilt, render the first page view close to the user with serverless or edge functions, and still call APIs for personalized data. The result is faster first loads and fewer bottlenecks from one origin machine.
-
In practice, the old pain was a browser loading a blank shell, then waiting on API calls. The newer pattern renders HTML on request at the edge, so the user sees a usable first screen before client side code finishes hydrating.
-
This is why Vercel and Netlify mattered. They bundled CDN, routing, deploys, serverless functions, and edge features into a front end workflow, so a React developer could ship dynamic behavior without standing up and operating a fleet of servers.
-
The trade off is not whether dynamic apps are possible, but where the breakpoints are. Startups and new product teams get speed and simplicity, while large enterprises often keep core systems on AWS and use Jamstack style stacks for new surfaces, docs, landing pages, and lighter apps.
This heads toward a world where the boundary between Jamstack and full stack apps keeps disappearing. Edge databases, server rendered React frameworks like Next.js and Remix, and better CDN level auth all push more of the app close to the user, which makes distributed compute the default way to build fast web software.