Urgent.News

What's breaking now, across hundreds of outlets.

Tech

Next.js Hosting for Headless CMS

If you want to use Next.js as the frontend for a headless CMS, this covers where to host it and what each option costs you in money and DevOps effort. On paper, Next.js runs anywhere Node.js runs, especially with the official Deployment Adapters API introduced in Next.js 16.2. In production it's a different story. A headless CMS frontend depends on multi-layered caching, webhook-driven…

When considering Next.js as the frontend for a headless CMS, there are several hosting options to choose from, each with its own costs and DevOps effort. In theory, Next.js can run on any environment where Node.js is supported, particularly with the official Deployment Adapters API introduced in Next.js 16.2. However, in practice, the caching features and edge functionality behave differently depending on the hosting platform.

The two main tiers for hosting Next.js with a headless CMS are managed and edge platforms, as well as direct enterprise cloud infrastructure. Managed and edge platforms, such as Vercel, Netlify, Kinsta, and Cloudflare Workers, handle aspects like virtual machine patching, load balancers, and CDN routing. Connecting a GitHub repository allows for live preview URLs of pull requests right away.

Vercel, being the reference implementation since it created and maintains Next.js, offers all Next.js features out of the box. However, cost predictability and procurement can become an issue for high-traffic media websites, leading to "Vercel bill shock" during scaling.

Netlify, which pioneered the decoupled CMS movement, provides a dedicated OpenNext adapter for Next.js that integrates with its CDN cache and Edge Functions. Netlify offers per-seat developer licensing and per-branch preview URLs. Kinsta's Application Hosting is a lesser-known option that provides persistent containerized Node.js applications on Google Cloud compute-optimized VMs with a Cloudflare Enterprise CDN included for DDoS protection and global edge caching. Kinsta bills by container resources without per-seat developer fees.

Cloudflare Workers emerge as a fourth option for high-bandwidth publishers who want global edge scale without managing virtual machines or paying Vercel's bandwidth markups. Cloudflare supports Next.js on Workers using vinext or the @opennextjs/cloudflare adapter. Cloudflare Workers provide zero egress bandwidth fees and serve static files from Workers Static Assets, next/image optimization to Cloudflare Images, and ISR and tag caches that bind to Cloudflare R2, KV, and Durable Objects.

However, Workers run on lightweight V8 isolates without full Linux VM support, and traditional persistent TCP connection pools may not be relied upon.

Rewritten by urgent.news; may contain errors — check the original.

Read the original at dev.to →

Report a problem with this story

More in Tech

Headless CMS Frontend Frameworks

If you want to pick a frontend framework for a headless CMS website, this covers the SPA and MPA options I'd consider and when each one fits.

  • SPA frameworks hydrate pages with JavaScript, leading to higher INP and memory leaks
  • MPA architectures serve static HTML, providing better Core Web Vitals and analytics performance
  • SPA and MPA each have distinct strengths and weaknesses for headless CMS frontends

Test 4.20 MHz Ultrasonic Protein Fibril Alignment in 48 Hours for $385 — Zero Microbes Required (Open-Source MRL-2 Bench Protocol)

Most discussions around synthetic biology or alternative protein biomanufacturing assume you need a sterile BSL-1 fermenter, a gas-diffusion electrolyzer, and weeks of strain engineering before you…

  • 48-hour, $385 bench protocol developed for testing ultrasonic protein fibril alignment
  • 4.20 MHz ultrasonic standing-wave cavity used to align dense protein suspensions
  • Open-source protocol invites hardware and physics builders to test and improve design

Private Browser File Uploads: Object Storage Service and 3-Stage Throughput

Short answer: for a marketplace accepting private browser uploads, the least complex design is a direct-to-object-storage upload followed by backend processing and an expiring download URL.

  • Private browser uploads use object storage service for direct upload
  • Three file sizes tested: 25 MB, 250 MB, 2 GB with 1, 10, 50 concurrent uploads
  • S3 recommended for ecosystem, but R2, GCS, Infrai viable alternatives

Advice for the next 100 Rust GUIs

  • Rust GUI landscape has expanded with two dozen toolkits announced
  • Performance issues persist in cross-platform GUI applications
  • GPUI framework enables high-performance Rust UI in real-world apps

More from Saturday 21 November →