// Articles
Guides, tutorials, and comparisons to help you build better backend applications.
Install Fiber v3, define routes and handlers, parse JSON bodies, add middleware and groups, then see when Encore fits as a Go backend framework with built-in infrastructure instead of a pure HTTP router.
Orchestration puts a central coordinator in charge of a multi-step process. Choreography lets services react to events and drive the next step themselves. When each pattern fits, and how Encore Pub/Sub supports event choreography without inventing a workflow engine.
Claude Code can edit a backend and open a pull request in minutes. The hard part is the deploy job: how the change reaches your AWS or GCP account without putting long-lived cloud keys in the agent session. This guide covers the safe way for AI agents to ship backend changes to your cloud.
Zero-downtime database migration keeps old and new application versions readable against one shared schema while you change it. Expand-contract steps, dual-write pitfalls, safe cutover, and how Encore applies Postgres up migrations automatically.
A bad backend release needs a rehearsed undo path: redeploy the previous image, watch database expand/contract rules, and use feature flags when compute alone cannot save you. How rollback works on AWS and Kubernetes, and how Encore environments and deploy history fit without inventing a one-click traffic switch.
CircleCI is a dedicated hosted CI service with orbs, caching and self-hosted runners. When teams look past it, GitHub Actions, GitLab CI, Buildkite and Jenkins are the usual picks. How they compare, and how application infrastructure still sits outside CI.
DevOps asked every team to own production. Platform engineering answers with golden paths and self-service. What changed for backend teams on AWS and GCP, and how infrastructure from code shrinks the custom platform surface.
GitOps keeps a Kubernetes cluster in sync with manifests in Git. The main tools, from Argo CD and Flux to Spinnaker and push-based pipelines, and when infrastructure from code replaces the manifest layer for application infra.
Hetzner Cloud sells cheap VMs with generous traffic from European and US locations. DigitalOcean adds managed databases, App Platform and Kubernetes on top of Droplets. How they compare for a typical backend, and when AWS or GCP is the better target.
GitHub Actions ships CI next to the repository on GitHub. Jenkins is a self-hosted automation server you operate. How they differ for backend teams, and how either one can hand the deploy stage to infrastructure defined in application code.
AI coding agents now propose and ship backend and infrastructure changes. Where that helps, which credentials and review gates still need a human, and how Encore is the safe way for AI agents to ship backend changes to your cloud.
A single VPS running Docker Compose is still a solid way to ship a small backend. Where that model wins, where multi-AZ managed cloud takes over, and how Encore deploys the same app to your own AWS or GCP account when one box is no longer enough.