How to deploy a backend to production without Kubernetes

Do you actually need Kubernetes?

Kubernetes is brilliant for large fleets with many teams and services. For a single backend, a handful of services, or a small team, it adds a mountain of complexity — control planes, YAML, networking, and a new vocabulary — to solve problems you may not have yet. Most products can run reliably on one or a few servers with a far simpler stack. Here's that stack.

Keep it running: a process manager

The single biggest difference between "it runs on my laptop" and "it runs in production" is a process manager. It restarts your app when it crashes and starts it on boot:

# systemd — the built-in option on every Linux box
# /etc/systemd/system/myapp.service
[Service]
ExecStart=/usr/bin/node /srv/app/server.js
Restart=always
Environment=PORT=3000
[Install]
WantedBy=multi-user.target

sudo systemctl enable --now myapp

Put a reverse proxy in front

Your app listens on a high port (e.g. 3000); nginx handles TLS and forwards traffic to it. This keeps your app off privileged ports and gives you one place for limits and headers:

server {
    listen 443 ssl;
    server_name example.com;
    ssl_certificate     /etc/letsencrypt/live/example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
    location / { proxy_pass http://127.0.0.1:3000; }
}

Deploy without downtime

The safe sequence: start the new version on a new port or instance, poll its health endpoint until it passes, point the proxy at it, drain and stop the old one. No window where nothing is serving. See the zero-downtime guide for blue-green, canary, and rolling in depth.