Read Replicas: How to Offload Database Load Without Breaking Your Application

Imagine: your project has grown, the main page receives 10,000 requests per second, and the master database is choking on SELECT queries. LCP shoots up to 5 seconds, users leave. The typical solution is to buy a more powerful server, but that's expensive and only provides temporary relief. We set up read replicas in a few days and distribute the read load horizontally. Turnkey: from infrastructure configuration to documentation for your team. Infrastructure cost savings are obvious: instead of one expensive machine, we use several cheap ones, with a lower total cost.

Problems That Read Replicas Solve

High CPU and I/O load. When one server handles both writes and reads, the buffer cache is quickly evicted. Hit rate drops, disk reads increase. Offloading reads to replicas reduces resource contention on the master—one client saw master CPU drop from 85% to 30%.

Long analytical queries. Reports with JOINs on millions of rows block transactions and slow user queries. We route such queries to a dedicated analytical replica with different memory settings (work_mem = 256MB, effective_cache_size = 8GB)—query time drops by 70%.

Geo-distributed users. If your audience is in different regions, deploy replicas in nearby data centers and direct read queries to them. We use Route 53 latency-based routing for automatic selection of the nearest replica.

Why Read Replicas Are Not a Silver Bullet

They don't solve write conflicts—inserts and updates still go to the master. Also, replication lag must be considered: with asynchronous replication, the replica may lag by seconds. Therefore, we always implement sticky sessions or LSN waiting (see below). Without it, you risk serving stale data.

How We Do It: A Real Case

One of our client systems: Laravel 10 on PostgreSQL 16, 50,000 unique visitors per day, the master handles 2000 req/s on average, of which 1700 are reads (85%). We deployed three read replicas—one for the public API, one for the admin panel, and one for reports. Setup took 4 days, including zero-downtime migration.

Key steps:

• Created replicas via pg_basebackup, set up asynchronous replication.
• Configured Laravel for read/write split with automatic balancing among replicas.
• For reports—a separate replica with adjusted parameters (work_mem = 256MB).
• Added lag monitoring in Prometheus with alerts at delay >30s.

Result: master load dropped 5x, LCP decreased from 3s to 0.8s, analytical queries no longer affect users.

How to Avoid Replication Lag Issues

After a write to the master, you cannot immediately read from a replica because data may not have copied yet. Solution: pass the write's LSN position to the client and, before reading, verify that the replica has caught up to that LSN. If not, redirect the query to the master. We embed this pattern directly into the application, preventing data races.

-- On master: get current LSN after INSERT
SELECT pg_current_wal_lsn();

# Example check on replica (pseudocode)
def read_after_write(lsn):
    if replica.is_caught_up(lsn):
        return replica.execute(query)
    else:
        return master.execute(query)

What to Do When Replication Lag Is Critical

If lag exceeds 60 seconds, a critical alert fires. Action plan:

1. Check if the replication process is blocked (pg_stat_replication).
2. Ensure the master has enough free space for WAL files.
3. Temporarily remove the replica from routing until it syncs.

Comparison of Synchronous and Asynchronous Replication

Example configuration for asynchronous replica (postgresql.conf):

hot_standby = on
hot_standby_feedback = on
max_standby_streaming_delay = 30s
wal_receiver_timeout = 60s

Process

1. Audit current load—collect metrics (CPU, IOPS, WAL generation), determine query profile.
2. Choose topology—how many replicas, synchronous or asynchronous, separate analytical replica if needed.
3. Configure replicas—create via pg_basebackup, tune postgresql.conf.
4. Application routing—Laravel config, pgBouncer R/W split, or custom middleware.
5. Monitoring and alerts—deploy Grafana dashboard, set notifications for lag.
6. Documentation and training—handover schema, credentials, instructions for promoting a replica to master.

What's Included

• Replication schema and configuration files (postgresql.conf, pgbouncer.ini).
• Application setup for read/write split (Laravel, Sequelize, Django ORM).
• Grafana dashboards with key metrics (lag, replica count, WAL size).
• Maintenance documentation (how to add a replica, what to do on failure).
• Training for your engineers—we demonstrate on our test environment.
• 30-day post-deployment support.

Timelines

Basic configuration with two replicas: 2 to 3 business days. If a large data migration (1+ TB) or global replication across multiple regions is needed, up to 5 days. We provide an exact estimate after auditing your system.

Comparison of approaches:

Our team has completed over 50 DB scaling projects. We guarantee that after setup, read performance improves at least 3x. Contact us for a free audit of your system. Order read replicas setup and receive documentation.

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.