OpenEdge — buckets, sites, an edge cache, and DNS

This runs your actual process — the thing a static host can't do. A release is built, started on its own port, and only receives traffic once it answers HTTP. A deploy that never comes up leaves the previous release serving, and a process that dies is restarted with backoff.

A deploy is an immutable set of files; the site points at one. That's why going live and rolling back are the same instant operation. Serve it at /s/<name>/, or set a domain and reach it by Host header.

A bucket is a namespace plus an access policy. Bytes are stored by content hash, so the same file uploaded twice is stored once and the hash is the ETag. Public buckets serve at /o/<bucket>/<key>; private ones need auth.

This is a real authoritative nameserver speaking RFC 1035 over UDP — not a mock. Test any record with dig @127.0.0.1 -p 5354 example.test. It answers for zones it holds and REFUSEs everything else, which is what an authoritative-only server should do.

The edge fetches from the origin once and serves everyone else from local storage until the TTL expires. Responses carry x-cache: HIT|MISS|EXPIRED and an age header. That's the whole CDN idea — the hard part at Cloudflare's scale is having 300 of these near your users, not the caching logic.