Master-Slave Replication: Eliminate the Database Bottleneck

Your web application slows down on report pages? The database can't handle user influx, and a single server is a single point of failure. We've seen this dozens of times: SELECT queries block INSERT, analytical reports bring down production, and backups on a live database cause downtime. Each such problem costs time and money. The solution is a turnkey master-slave replication setup. We guarantee fault tolerance and offload the primary server, proven on 100+ projects.

Replication (Master-Slave or Primary-Replica) is asynchronous or synchronous data transfer from the primary server to one or more replicas. It allows scaling read operations: up to 80% of queries can be directed to replicas, leaving the master for writes only. This reduces latency and eliminates resource contention. With our experience configuring 50+ projects, we implement this architecture in 1–3 days.

Why Is Master-Slave Replication Critical for Your Application?

Without replication, you risk:

• Outage: on master failure, data is unavailable until recovery. Average manual downtime: 2–4 hours.
• Degradation: analytical queries block writes, increasing TTFB by 3–5 times.
• Expensive backups: dumping a live master locks tables, causing downtime.

Compared to a single database, an architecture with one replica handles up to 5 times more read queries. With ProxySQL, the improvement can reach 10x. For example, an e-commerce project after replication reduced report query response time from 12 seconds to 0.8 seconds—15 times faster.

When Should You Use Synchronous Replication?

Synchronous replication guarantees zero data loss on master failure. It is essential for financial transactions or data-critical applications. However, the cost is a 30–50% increase in write latency and reduced throughput. We recommend synchronous mode for the core application and asynchronous for analytics.

How We Set Up Replication in PostgreSQL and MySQL

We use only proven approaches: streaming replication for PostgreSQL and GTID-based replication for MySQL. Key differences are shown below:

Typical configuration mistakes: incorrect wal_level (should be replica or logical), insufficient max_wal_senders for multiple replicas, ignoring replication lag (no monitoring), and writing to a replica in read-only mode—often causes data mismatch.

Example PostgreSQL master configuration:

# postgresql.conf
wal_level = replica
max_wal_senders = 10
wal_keep_size = 1GB
synchronous_commit = on
synchronous_standby_names = 'replica1'

Initializing the replica:

pg_basebackup -h master -U replication -D /var/lib/postgresql/14/main -P -Xs -R

Example MySQL master configuration:

[mysqld]
server-id = 1
log_bin = /var/log/mysql/mysql-bin.log
binlog_format = ROW
gtid_mode = ON
enforce_gtid_consistency = ON

Starting the MySQL replica with GTID:

CHANGE MASTER TO MASTER_HOST='192.168.1.10', MASTER_USER='replication', MASTER_PASSWORD='xxx', MASTER_AUTO_POSITION=1;
START SLAVE;

Routing reads through ProxySQL:

INSERT INTO mysql_servers(hostgroup_id, hostname, port) VALUES (10, 'master', 3306);
INSERT INTO mysql_servers(hostgroup_id, hostname, port) VALUES (20, 'replica', 3306);
INSERT INTO mysql_query_rules(rule_id, active, match_pattern, destination_hostgroup) VALUES (1, 1, '^SELECT', 20), (2, 1, '.*', 10);
LOAD MYSQL SERVERS TO RUNTIME; LOAD MYSQL QUERY RULES TO RUNTIME;

What Does the Replication Setup Process Include?

1. Audit current load and architecture: measure peak RPS, latency, database size.
2. Choose topology: single or multiple replicas, asynchronous or synchronous.
3. Configure master: wal_level, max_wal_senders, gtid_mode.
4. Initialize replicas via pg_basebackup or mysqldump.
5. Set up routing (ProxySQL / pgBouncer) and split read/write queries.
6. Monitor lag: Prometheus + Grafana with alerts at >60 seconds.
7. Document configuration and failover procedures, train the team.

Comparison of Asynchronous vs Synchronous Replication

What the Work Includes

• Full documentation of configuration and failover procedures.
• Backups and scripts for quick recovery.
• Access to monitoring (Grafana, Telegram alerts).
• Team training: how to check replication status and perform switchover.

Timelines and Cost

Timeframes depend on complexity:

• One replica + basic monitoring: 1 day.
• Replication with ProxySQL and failover: 2–3 days.

Cost is determined individually after analysis. However, the investment pays off quickly: infrastructure savings from read replicas can reach 40%, and recovery time after failure drops from hours to minutes. A typical project pays off in 2–3 months. If you already have a project, contact us for a free assessment and get a fault-tolerant architecture.

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.