Render: A Full PaaS Topology of Web, Private, Worker, and Cron Services

🌏 中文版

Render is a general-purpose PaaS deploying Static Sites, Web Services, Private Services, Background Workers, Cron and Workflows from Git or images. It also provides Postgres, Key Value, private networking, TLS, previews, health checks, and Blueprint IaC.

Service types are lifecycle contracts

A Web Service binds a public port for HTTP and WebSocket. A Private Service has an internal hostname and port in the regional private network. A Background Worker has no inbound listener and polls a queue. Cron executes on schedule and exits. Do not disguise workers as web services or use private services for listener-free processes.

Workers and cron jobs need idempotency. Deployment and scaling send termination signals, so stop taking work and finish or requeue in-flight jobs. Health endpoints should prove serving ability without expensive full dependency checks.

Blueprints make topology reviewable

The Blueprint specification declares services, databases, regions, plans, build and start commands, health checks, environment groups, and deploy hooks. Review it in the repository and reference platform secrets instead of writing values in YAML. Pre-deploy migrations must tolerate overlapping old and new instances and rollback.

Previews create real resources. Configure cleanup, budgets, isolated credentials, and sanitized data so every pull request does not leave databases and public endpoints behind.

Persistent disks change HA semantics

Filesystems are ephemeral by default. A persistent disk retains state but limits multi-instance scaling, zero-downtime deployment, and job access. Prefer managed or external clustered data services for production. A single-node stateful disk accepts a failover and maintenance boundary and needs independent backups.

Render fits small and medium polyglot products combining APIs, private services, workers, cron, and databases. Vercel or Netlify offer deeper frontend and edge integration; Fly.io exposes more global placement and networking. Deploy a bad release, stop a worker, redeliver jobs, lose data services, and restore backups to test rollback, draining, alarms, and Blueprint drift.

References

• Render service types
• Render web services
• Render private services
• Render background workers
• Render Blueprint specification
• Render persistent disks