Back to Posts

Edge Caching, Preview, and Multidev for Decoupled Sites

•5 months ago
PerformanceNext.jsWebOps
How Pantheon delivers decoupled sites fast — edge caching on the Global CDN, Multidev previews, and on-demand revalidation.
Next.js pages cached at global edge nodes with multidev preview branches.

Speed is the whole point of going decoupled, and on Pantheon it comes from the platform rather than from glue code. Server-rendered Next.js responses are cached in Pantheon's Global CDN with persistent caching, so most web requests hit the edge instead of your application. The Next.js runtime is container-based on Google Cloud Run and scales automatically through traffic spikes.

The workflow stays fast, too. Pantheon's GitHub App builds and deploys on every push, and each pull request gets its own Multidev preview environment so editors and reviewers can see changes before they ship. Drupal's draft preview wires straight into the Next.js frontend through the demo's /api/draft and /api/revalidate routes, giving editors on-demand revalidation when content changes.

Governance is built in: role-based access control, dev → test → live environments with review checkpoints, encrypted connections, and contract-based pricing with no per-invocation surprises.

Details on the Next.js platform page and in the caching documentation.

Edge Caching, Preview, and Multidev for Decoupled Sites | NextJS on Pantheon