PostgreSQL RTO and RPO: Setting Up High Availability with Patroni

Note: when a service is down for an hour and recovery takes a day, that's a catastrophe. A payment gateway processing 10,000 transactions per minute, idle for 30 minutes, loses not only revenue but also customer trust. The average cost of an hour of downtime for e-commerce can be substantial. RTO (Recovery Time Objective) and RPO (Recovery Point Objective) are the parameters that determine how fast you get back on your feet after a failure and how much data you lose. We configure PostgreSQL infrastructure so that these metrics meet business requirements: from cold standby to multi-region active-active. Our engineers have over 10 years of PostgreSQL experience and more than 50 successful projects implementing fault-tolerant clusters.

What Problems We Solve

• Undefined SLA. Without formal RTO/RPO, you cannot guarantee recovery time to clients. Contractual penalties pile up, and reputation suffers.
• Manual recovery. On failure, an administrator manually promotes a replica — this means hours of downtime. Automatic failover reduces RTO to seconds.
• Data loss. Infrequent backups (once a day) mean RPO = 24 hours. On failure, you lose a day's transactions. WAL archiving every 5 minutes reduces RPO to 5 minutes.
• Excessive costs. Chasing zero RTO without business analysis leads to overspending. We help find the cost/reliability balance.

How to Determine RTO and RPO for Your Business

The first step is estimating the cost of downtime. We use a simple calculator:

class RtoCalculator:
    def calculate_downtime_cost(self, hourly_revenue, churn_per_hour, penalty, clv, customers):
        costs = {
            'lost_revenue': hourly_revenue,
            'churn': (churn_per_hour/100)*customers*clv,
            'sla_penalties': penalty,
            'labor': 500
        }
        total = sum(costs.values())
        if total > 100000: return '< 5 min (active-active)'
        elif total > 10000: return '< 15 min (hot standby)'
        else: return '< 1 h (warm standby)'

Why Patroni Is the Best Choice for PostgreSQL

Patroni with etcd provides failover in 30 seconds — 10 times faster than manual recovery. It manages configuration, automatically switches traffic, and loses no data when synchronous replication is properly configured. It is the standard for High Availability in PostgreSQL.

How We Do It

Case study: A corporate CRM on PostgreSQL 15. Required RTO < 30 minutes and RPO < 5 minutes. We deployed Patroni on three nodes, pgBackRest for WAL archiving to S3, and HAProxy for routing. After a test failure (kill primary), failover took 18 seconds, data loss was 0 (synchronous replication). Recovery documentation was handed over to the team.

# postgresql.conf
wal_level = replica
archive_mode = on
archive_command = 'pgbackrest --stanza=main archive-push %p'
checkpoint_timeout = 5min
max_wal_senders = 10
wal_keep_size = 1GB

# pgbackrest.conf
[global]
repo1-type=s3
repo1-s3-bucket=myapp-wal-archive
repo1-retention-full=4
repo1-retention-diff=14

[main]
pg1-path=/var/lib/postgresql/data

Patroni: Automatic Failover (RTO < 30 sec)

# patroni.yml
scope: postgres-cluster
name: pg-node-1
restapi:
  listen: 0.0.0.0:8008
etcd3:
  hosts: etcd1:2379,etcd2:2379,etcd3:2379
bootstrap:
  dcs:
    ttl: 30
    loop_wait: 10
    max_lag_on_failover: 1048576
postgresql:
  parameters:
    wal_level: replica
    hot_standby: on
    archive_command: 'pgbackrest --stanza=main archive-push %p'

HAProxy: Role-Aware Routing

frontend postgres_write
  bind *:5432
  default_backend postgres_primary
backend postgres_primary
  option httpchk GET /master
  server pg-node-1 check port 8008

frontend postgres_read
  bind *:5433
  default_backend postgres_replicas
backend postgres_replicas
  balance roundrobin
  option httpchk GET /replica
  server pg-node-1 check port 8008

How to Monitor RTO/RPO

Monitoring is key to SLA compliance. The table below lists metrics to track:

We set up Prometheus + Alertmanager. When RPO is breached, the on-call team gets notified. This allows reaction before the failure impacts business.

What to Do When RPO Is Breached

Typical mistakes in designing fault tolerance:

• Lack of failover tests. We perform chaos engineering: simulate node, network, and disk failures. Only then can real RTO/RPO be validated.
• Ignoring replication lag. In synchronous mode, latency between data centers must not exceed 10 ms.
• Incorrect backup rotation. pgBackRest with retention (full/diff) ensures old backups are not overwritten. Point-in-time recovery is supported.

We create an incident runbook for on-call staff: steps to take on failure, promotion procedure, vendor contacts.

Process

1. Audit — inventory current infrastructure, load, budget.
2. Calculation — determine target RTO/RPO together with you.
3. Design — select architecture (Patroni + etcd, pgBackRest, HAProxy).
4. Implementation — deploy, configure, test failover.
5. Testing — simulate failures, measure actual RTO/RPO.
6. Documentation and training — incident runbook, on-call training.

What Is Included in Turnkey Setup

• Configuration of Patroni with etcd/Consul for automatic failover
• pgBackRest — full/differential backup, WAL archiving to S3 or local storage
• HAProxy — intelligent routing (write/read split)
• Monitoring — Prometheus exporter for lag, alerts on RPO breaches
• Documentation — recovery plan, configs, checklists
• Training — 2-hour workshop for your team

Timeframes and Guarantees

Turnkey setup for a typical 3-node cluster takes 3–5 business days. The result: target RTO/RPO achieved, confirmed by load testing. We are certified engineers with over 10 years of PostgreSQL experience. We guarantee SLA on recovery time.

Savings from automated failover can be significant per month by preventing downtime. Contact us for a calculation of your case. Request a consultation — we will select the optimal architecture for your budget and requirements.

We regularly encounter a situation: "The site is not opening" at 3 a.m. — and it turns out that the VPS disk is full because nginx logs haven't been rotated for six months. Or the server went down under load on the day of an advertising campaign launch because the shared hosting had a limit of 50 concurrent connections. Setting up hosting and deployment is not about "where it's cheaper" but about what happens when something goes wrong. Our team helps avoid such incidents by designing infrastructure that accounts for real load patterns.

When to choose Vercel and Netlify?

Vercel is built for Next.js — deploy in one push, preview deployments for every PR, automatic CDN, Edge Functions, ISR without configuration. For frontend projects and JAMstack, it's the optimal choice: no operational overhead, time-to-deploy measured in minutes.

Real limitations: Vercel Serverless Functions run in us-east-1 by default (latency for Europe +80–100ms), Function timeout 300 seconds on Pro, Bandwidth 1TB/month on Pro. For heavy backend, you need workers or a separate server.

Netlify is closer to static sites and Edge Functions based on Deno Deploy. Build minutes are the main limitation on the free tier.

Why is Docker the foundation of predictable deployment?

"It works on my machine" — classic. Docker solves this through environment containerization. But a bad Dockerfile creates new problems.

A typical mistake: copying everything into the image without .dockerignore, resulting in an 800MB image instead of 80MB. node_modules inside the image weighs as much. Correct approach: multi-stage build.

FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
RUN npm run build

FROM node:20-alpine AS runner
WORKDIR /app
COPY --from=builder /app/.next ./.next
COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/package.json ./package.json
EXPOSE 3000
CMD ["npm", "start"]

Final image: 180MB instead of 1.2GB. CI build time is reduced due to layer caching — if package.json hasn't changed, the layer with npm ci is taken from cache.

Docker Compose for local development and simple production scenarios: application + PostgreSQL + Redis in one configuration. For production on a single server, it's a perfectly viable option if there's no requirement for horizontal scaling.

More about containerization — Wikipedia: Docker.

How to set up Nginx as a reverse proxy?

Nginx in front of the application is standard for VPS and dedicated servers. Main functions: SSL termination, gzip, static files, rate limiting, upstream load balancing.

A configuration often done incorrectly: worker_processes auto — number of processes equals CPU count. worker_connections 1024 — that's 1024 per worker process. With 4 CPUs and 1024 connections = 4096 concurrent connections. For a high-traffic site, you need worker_connections 4096 and set keepalive_timeout 65.

For static assets with hash in the filename:

location ~* \.(js|css|woff2|png|webp)$ {
    expires 1y;
    add_header Cache-Control "public, immutable";
}

immutable tells the browser: don't revalidate this file even on hard refresh. This only works correctly with content-hashed filenames (which Vite/webpack do by default). Documentation — Wikipedia: Nginx.

AWS: flexibility and complexity

EC2 + Auto Scaling Group — classic for horizontal scaling. AMI with pre-installed application, Launch Template, ASG with min/desired/max instances, Application Load Balancer. When CPU > 70% for 3 minutes — scale out, when CPU < 30% for 15 minutes — scale in. Health check via ALB removes unhealthy instances from rotation.

ECS Fargate — containers without managing EC2. Deploy a Docker image, specify CPU/memory (512 CPU units = 0.5 vCPU, from 512MB memory), Fargate launches it. More expensive than Lambda, but no cold start and no timeout limitations. Suitable for long-running processes, WebSocket servers, heavy workers.

RDS for PostgreSQL with Multi-AZ: automatic failover in 1–2 minutes when primary fails. Read Replicas for scaling reads. RDS Proxy for connection pooling — Lambda functions cannot hold long-term connections, the proxy buffers this.

Kubernetes: when it is justified

K8s adds significant operational complexity. Justified when: multiple teams deploy independent services, fine-grained resource allocation per service is needed, canary deployments and blue/green without downtime are required.

AWS EKS, GKE, or managed k8s from Hetzner (cheaper). Helm charts for standard services. Horizontal Pod Autoscaler based on CPU and custom metrics (RPS via Prometheus).

For most startups and medium-sized projects, Kubernetes is overkill. ECS or Fly.io provide 80% of the capabilities with 20% of the operational complexity.

Monitoring and alerting

A server without monitoring is waiting for an incident. Minimal stack: Prometheus + Grafana (or Grafana Cloud for managed), alerting on disk > 80%, memory > 85%, CPU > 90% over 5 minutes, error rate > 1%. Uptime via Better Uptime or Upptime (self-hosted).

Logs: Loki + Grafana or CloudWatch Logs Insights. Structured JSON logs (winston, pino) are mandatory — otherwise, log searching becomes a pain.

What is included in hosting setup

• Audit of current infrastructure and load profiling
• Selection of target architecture (VPS, AWS, serverless, Kubernetes)
• Setting up CI/CD pipeline (GitHub Actions, GitLab CI) with automatic deployment
• IaC via Terraform or Pulumi (infrastructure as code)
• Configuration of Nginx, SSL certificates, HTTP/2, brotli
• Monitoring and alerting (Prometheus + Grafana, PagerDuty)
• Documentation of runbooks and team training

Additionally, contact us if you need migration from current hosting or integration with external services.

Work process

1. Audit of current infrastructure (2–5 days)
2. Selection of target architecture with load and budget justification (1–3 days)
3. Setting up CI/CD pipeline (GitHub Actions, GitLab CI) (2–5 days)
4. IaC via Terraform or Pulumi (3–10 days)
5. Setting up monitoring and alerting (2–5 days)
6. Documentation of runbooks and team training (1–3 days)

Our experience — 7 years on the market, over 50 projects, guarantee of operability after deployment.

Timeline

• Basic deployment on VPS with Docker + Nginx + CI/CD: 1–2 weeks.
• Setting up AWS infrastructure with Auto Scaling, RDS, CDN: 3–6 weeks.
• Migration to EKS from scratch: 6–12 weeks.
• Setting up Vercel/Netlify for JAMstack: 3–5 days.

The cost is calculated individually depending on complexity and scope of work. Get a consultation — we'll evaluate your architecture in one day.