Setting up Redis Sentinel for High Availability

We often encounter a situation: the Redis master fails, and the application loses cache or sessions for several minutes. Manual switching to a replica takes 5–15 minutes of downtime, lost transactions, and stress. Without automation, you have to manually log in to the server, run SLAVEOF NO ONE, and reconfigure client applications. This is time-consuming and error-prone, especially during nights or weekends. The solution is Redis Sentinel: a system that automatically detects master failure, promotes a new master, and notifies clients. Sentinel is 10 times faster than manual switching—failover takes 10-20 seconds. Client libraries like phpredis and predis support automatic redirection to the new master without code changes. With proper configuration, the application loses at most 20 seconds of connection before resuming with the new replica.

Why three Sentinels?

Sentinel uses a voting algorithm: when contact with the master is lost, each Sentinel proposes promoting a replica. A decision is made only with a quorum—a majority of votes. With two Sentinels, split-brain is possible (each considers its candidate master). Three servers with quorum = 2 guarantee a correct failover.

How to configure Redis Master and Replica in 6 steps

1. Install Redis on all three servers (same version, e.g., 7.2).
2. Configure the master—set passwords, memory limit, enable AOF.
3. Configure replicas—add parameter replicaof <master-ip> 6379.
4. Configure Sentinel—create sentinel.conf with monitor, password, and timeout settings.
5. Start Sentinel on all servers with redis-sentinel /etc/redis/sentinel.conf.
6. Check the status—run SENTINEL masters to confirm the master is detected.

Example master config (/etc/redis/redis.conf):

bind 0.0.0.0
port 6379
requirepass RedisPassword123
masterauth RedisPassword123
maxmemory 4gb
maxmemory-policy volatile-lru
appendonly yes
appendfsync everysec
protected-mode no

Replica config is the same but add replicaof <master-ip> 6379 and replica-read-only yes.

Example Sentinel config (/etc/redis/sentinel.conf on each server, only sentinel announce-ip changes):

port 26379
daemonize yes
logfile /var/log/redis/sentinel.log
sentinel monitor mymaster <master-ip> 6379 2
sentinel auth-pass mymaster RedisPassword123
sentinel down-after-milliseconds mymaster 5000
sentinel parallel-syncs mymaster 1
sentinel failover-timeout mymaster 60000
sentinel notification-script mymaster /opt/redis/notify.sh
sentinel announce-ip <server-ip>
sentinel announce-port 26379

How to test failover without risk?

We recommend simulating before production:

1. Stop the master: systemctl stop redis.
2. Observe Sentinel logs—failover should begin within 5–15 seconds.
3. Check the new master: SENTINEL master mymaster—the ip field will change.
4. Start the old master again: systemctl start redis—it will automatically become a replica of the new master.

Common testing mistakes:

• Passwords not verified—failover may fail due to auth-pass.
• Too large down-after-milliseconds—delay up to 30 seconds.
• Missing notification-script—you won't know about master change.

Comparison: Sentinel vs. Redis Cluster

For 90% of projects with data volumes up to 64 GB, Sentinel is the optimal choice.

Comparison of downtime

By automating, you save dozens of hours per year and eliminate human error.

What is included in the turnkey setup

We provide:

• Configuration of Master+Replica+Sentinel on 3 servers
• Quorum and failover mechanism verification
• Notification setup (Telegram, email) on master change
• Failover test script
• Client integration (Laravel, Symfony, plain PHP)
• Operations documentation

We have implemented Sentinel in over 50 projects—experience shows that 80% of incidents resolve automatically without engineer intervention. According to official Redis Sentinel documentation, this configuration ensures 99.9% availability when properly configured.

Timeline and guarantees

Standard setup of Sentinel with three servers, failover testing, and integration takes 1 to 2 business days. Cost is calculated individually. The investment pays off through reduced downtime. We offer a 30-day guarantee on the correct operation of the fault tolerance scheme.

Order Redis Sentinel setup—and forget about manual switching. Get an engineer consultation to estimate the cost for your project.

Note: In the configurations above, use your own password and IP addresses. Do not forget to open ports 6379 (Redis) and 26379 (Sentinel) in the firewall.

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.