Overview
CDB EdgeCompute runs custom code on CDB edge servers close to end users, with no servers to set up or maintain. The code is one of two application types: an HTTP application answers requests sent to its own URL, and a CDN application changes the requests and responses passing through a CDN resource.
Build and deploy
Choose between two application types:
CDN applications must be attached to a CDN resource before they can process live traffic.
HTTP applications can also be deployed without code from built-in templates: Geolocation redirect sends end users to a URL chosen by country, and Markdown renderer turns Markdown files into HTML pages.
Manage and reuse applications
Change a deployed application and reuse its setup.
Local development
An application can be built and tested on a local machine before it is deployed. The local development tools fit different workflows: asking a coding agent (Claude Code, Codex, or Cursor), working in VS Code, running automated tests in CI, or running a binary from a terminal with edgecompute-run.
Data and secrets
Decide where an application keeps the data and credentials it uses at runtime.
Monitoring and troubleshooting
Check how an application is behaving, find the cause of a failed request, and follow how long requests take.
- Metrics and logs: response status counts and the log entries for each request.
- Troubleshooting: CDB EdgeCompute status codes 530 to 533 and debug logging.
- Grafana: how long applications take to run, and how that duration changes over time.