Table of Contents
🌏 中文版
Netlify grew from static and Jamstack hosting into a web platform. Git builds, global delivery, Functions, Deno-based Edge Functions, background and scheduled functions, Blobs, Database, Forms, and Image CDN share one site and deploy workflow.
Atomic deploy is the core semantic
The deploy overview explains that a deployment uploads fully before switching the public URL, avoiding mixed HTML and assets. Each version has an immutable permalink, pull requests get Deploy Previews, and rollback repoints traffic.
Application data does not roll back. Use expand-and-contract migrations and test client/server skew. Give previews separate environments and credentials plus password or team protection to avoid exposing unreleased content and production side effects.
Functions and Edge Functions differ
Netlify Functions fit SSR, APIs, and Node-style server code near data. Background Functions handle longer asynchronous work; Scheduled Functions trigger by time. Edge Functions run in a Deno-based edge runtime for redirects, personalization, auth gates, and request or response transforms. They do not suit heavy Node-native dependencies or repeated access to a distant single-region database.
Adapters compile framework routes into function and edge artifacts. Inspect deploy summaries after framework or plugin upgrades instead of trusting local development alone.
Separate deployment and durable state
Static files and deploy-scoped caches follow deployment versions; Blobs and Database persist. Deliberately choose deploy-specific or cross-deploy stores, tenant keys, consistency, backup, and deletion. Preview access to production blobs still requires authorization.
Netlify fits content and frontend-heavy sites, atomic deploys, preview collaboration, and modest serverless or edge logic. Compare Vercel for deep Next.js integration and Render for containers, private networks, workers, disks, and backend topologies. Roll back a deploy while keeping the new schema, redeliver background work, and test runtime regions and cache invalidation.
References
Loading...