PostgreSQL Replication Setup with Automatic Failover

Your web application is growing: 10,000 queries per second, the database is choking, LCP has climbed to 3 seconds. Users are leaving. The solution is setting up Master-Slave replication on PostgreSQL. This also saves up to 40% on read infrastructure costs—replicas can run on cheaper instances. Our master-slave replication solution uses WAL streaming and Patroni for automatic failover, ensuring a high-availability database. We handle complete PostgreSQL replication setup including pg_hba configuration and replication slots. We configure a resilient cluster in 2-3 days.

Challenges We Address with Master-Slave Replication

At 10,000 read queries per second, replication reduces LCP from 3 seconds to 200 ms. We use hot standby—replicas serve SELECT queries, offloading the primary. Synchronous replication guarantees zero data loss but consumes 30% more resources due to waiting for acknowledgment. Asynchronous replication is faster but may lose the last transaction (less than 1% loss on failure). Choice depends on consistency requirements: for financial systems—synchronous, for web apps—asynchronous. Infrastructure budget savings can reach 30-50% by using replicas for reads.

How We Set Up Automatic Failover with Patroni

Patroni is the standard for automatic PostgreSQL failover in production. It uses a distributed lock via etcd. When the primary fails, Patroni automatically promotes the replica with the smallest lag, minimizing downtime to under 10 seconds. For example, Patroni is 3x faster than repmgr in failover scenarios, reducing downtime from 30s to under 10s. Operational costs are reduced by 40% by using replicas for reads and avoiding expensive high-availability hardware.

Setup steps:

1. Deploy an etcd cluster of 3 nodes.
2. Install Patroni on each PostgreSQL server.
3. Configure Patroni with etcd endpoints.
4. Start Patroni—it automatically elects a master.
5. Configure HAProxy to route write queries to master and read queries to replicas.

How We Configure Replication

Architecture: The application writes only to the primary; reads go to replicas. WAL is transferred via streaming replication.

# Primary postgresql.conf
wal_level = replica
max_wal_senders = 5
wal_keep_size = 1GB
max_replication_slots = 5
synchronous_commit = on

# pg_hba.conf
host replication replicator 10.0.1.0/24 scram-sha-256

# Create replication user (run on primary)
-- CREATE ROLE replicator WITH REPLICATION LOGIN PASSWORD 'strong_password';

# On replica: run pg_basebackup
# pg_basebackup -h 10.0.1.10 -U replicator -D /var/lib/postgresql/14/main -P -Xs -R

# Replica postgresql.conf
hot_standby = on
hot_standby_feedback = on
max_standby_streaming_delay = 30s

-- Monitoring replication slots
SELECT slot_name, active, restart_lsn, confirmed_flush_lsn,
       pg_size_pretty(pg_wal_lsn_diff(pg_current_wal_lsn(), restart_lsn)) AS lag_bytes
FROM pg_replication_slots;

-- Monitoring replica lag
SELECT application_name, client_addr, state, write_lag, flush_lag, replay_lag
FROM pg_stat_replication;

Comparison: Synchronous vs. Asynchronous Replication

Comparison: Failover Tools

What Automatic Failover with Patroni Delivers

Automatic failover eliminates manual intervention when the primary fails. Downtime is reduced to under 10 seconds, critical for services requiring 99.9% uptime. Additionally, Patroni allows planned switchovers without stopping the application.

What Is Included in the Work (Deliverables)

This work includes the following deliverables:

• Deployment of Master and 1-2 replicas with optimized WAL parameters.
• Configuration of pg_hba, replication slots, and monitoring.
• Setup of PgBouncer for connection pooling and request routing.
• Installation and configuration of Patroni with etcd for automatic failover.
• Application integration: configuring read/write routing.
• Lag and performance monitoring (Prometheus + Grafana).
• Documentation: detailed operational guide.
• Access: SSH keys, database credentials, monitoring dashboards.
• Training: 2-hour session for your team.
• Support: 1 month of post-launch support.

Timelines and Cost

• Basic setup (Master + 1 replica, without failover): 1 day.
• Full cluster with Patroni and monitoring: 2-3 days.

Cost is calculated individually based on infrastructure complexity. Basic setup costs start at $2,000, and automatic failover adds $1,500. Potential monthly savings on read infrastructure exceed $1,000. Get a consultation—we will analyze your project free of charge and propose the optimal solution. Order the setup now and ensure 99.9% uptime!

Our Experience

We have completed over 50 projects configuring PostgreSQL clusters for web applications with loads up to 100,000 queries per second. Our engineers hold PostgreSQL Professional certifications and regularly speak at industry conferences. We guarantee quality and post-launch support.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.