Docker Compose

Mon, 01 Jan 0001 00:00:00 +0000

backd deliberately leaves some protections to the infrastructure around it: TLS, request rate limits and sign-up spam, body size limits at the edge, and database security. The repository ships a reference deployment that puts all of these in place. It lives in deploy/production/, and CI tests it end to end on every change.

The protections themselves are the same on every platform (Production deployment); this page is how Docker Compose does them. For a cluster, see Kubernetes.

Kubernetes

Mon, 01 Jan 0001 00:00:00 +0000

deploy/kubernetes/backd is a Helm chart for backd on any Kubernetes cluster; DigitalOcean shows the whole path on one provider. The chart creates no infrastructure and no secret: the objects it reads (Secrets and a ConfigMap) are made by whatever builds the cluster, which for DigitalOcean is the Terraform in deploy/terraform/digitalocean.

The workloads

It maps the production reference one to one:

Deployment	Image	What it does	Reads the configuration
`backd`	your configuration image	the public API (no admin API, no change stream)	yes
`backd-realtime`	your configuration image	the only pods that read the change stream (realtime) and hold the trigger lease	yes
`backd-admin`	your configuration image	the admin API and interface	yes
`worker`	your configuration image	async jobs and cron	yes
`executor`	`ghcr.io/fernandezvara/backd-executor`	one Deno process per function call	no
`egress`	`ghcr.io/fernandezvara/backd`	the only way out for functions and push	no
`backd-provision` (Job)	your configuration image	`backd-server provision`, before an install, an upgrade or a rollback	yes

Each is replicas.<name> in the values, and replicas.default is used by every component without a number of its own. A component with more than one pod gets a PodDisruptionBudget. Use one namespace per installation: the Services have fixed names.

Production deployment on back(d)

Docker Compose

Kubernetes

The workloads#

The workloads