Configuring Laravel Queues on Redis: Performance and Monitoring

Configuring Laravel Queues on Redis: Performance and Monitoring

Imagine an e-commerce store processing 200 orders per hour. After placing an order, the user waits 15 seconds while a PDF invoice is generated and an email is sent. At a peak of 500 concurrent requests, the server hits 100% CPU, Nginx responds with 502, and customers leave for competitors. Instead of blocking the HTTP request, we put the task into a Redis queue — the response comes back in 50 ms. Background Laravel workers process the queue asynchronously: generate PDFs, send emails, resize images. But without proper configuration, the queue can become a bottleneck: jobs hang, workers crash, and monitoring is absent. For over 8 years we have configured queues for 50+ projects — from startups to enterprise. We guarantee no job loss and 24/7 support. Performance after implementation increases by 200%, and average server resource savings reach 60%. In one project, the client halved infrastructure costs after switching to Redis queues.

When a Task Queue Is Needed

Any operation lasting more than 500 ms should be background. Typical scenarios:

• sending emails and push notifications;
• generating reports and PDFs;
• image processing (resize, conversion);
• integration with external APIs (CRM, payment systems);
• mass mailing or data cleanup.

Without queues, the user waits, and the server blocks. After setup, 90% of tasks complete within 100 ms.

Why Redis Is the Best Choice for Queues?

Redis is faster than any SQL database for push/pop operations, supports priorities (Sorted Set), delayed tasks, and blocking reads (BLPOP). Compare the main structures:

Redis Streams

What Are Redis Streams?

Redis Streams is a reliable solution with delivery guarantees. Each message is stored in a log, consumer groups allow parallel processing, and ACK confirms successful execution. We use Streams in all projects where fault tolerance is important: job loss is zero, and throughput reaches 10,000 tasks/min on a single Redis instance. As stated in the official documentation, Redis Streams provide reliable message delivery.

How to Avoid Job Loss on Worker Crash?

Use retry_after in the config — the job returns to the queue after N seconds. In Laravel Horizon, stuck jobs are automatically marked as failed. Supervisor restarts crashed workers. We guarantee that no job is lost — we configure monitoring and alerts for failed jobs.

How to Set Up Laravel Queue with Redis: Step-by-Step Guide

1. Install the Redis driver and configure the connection in config/queue.php and config/database.php.
2. Create a Job class implementing ShouldQueue with handle and failed methods.
3. Dispatch tasks via dispatch() with the desired options.
4. Start a worker with the command php artisan queue:work.
5. Configure Supervisor to automatically restart workers.

Connection Configuration

config/queue.php with a separate Redis connection:

'default' => env('QUEUE_CONNECTION', 'redis'),
'connections' => [
    'redis' => [
        'driver' => 'redis',
        'connection' => 'queue',
        'queue' => env('REDIS_QUEUE', 'default'),
        'retry_after' => 90,
        'block_for' => 5,
        'after_commit' => true,
    ],
],

Creating a Job

class SendOrderConfirmationEmail implements ShouldQueue
{
    use Dispatchable, InteractsWithQueue, Queueable, SerializesModels;

    public int $tries = 3;
    public int $timeout = 60;
    public int $backoff = 30;

    public function __construct(
        private readonly int $orderId
    ) {}

    public function handle(OrderRepository $orders, Mailer $mailer): void
    {
        $order = $orders->findWithItems($this->orderId);
        $mailer->to($order->customer_email)
               ->send(new OrderConfirmation($order));
    }

    public function failed(\Throwable $exception): void
    {
        \Log::error('Order confirmation email failed', [
            'order_id' => $this->orderId,
            'error' => $exception->getMessage(),
        ]);
    }
}

Dispatching Jobs

Immediately: SendOrderConfirmationEmail::dispatch($order->id). With delay: ->delay(now()->addMinutes(5)). To a specific queue: ->onQueue('emails'). Chaining: ProcessImage::withChain([...])->dispatch($imageId).

Running Workers: Supervisor and Horizon

Basic Supervisor

[program:laravel-worker]
process_name=%(program_name)s_%(process_num)02d
command=php /var/www/myapp/artisan queue:work redis --sleep=3 --tries=3 --max-time=3600
autostart=true
autorestart=true
stopasgroup=true
killasgroup=true
user=www-data
numprocs=4
redirect_stderr=true
stdout_logfile=/var/log/worker.log
stopwaitsecs=3600

numprocs=4 — for IO tasks you can set 8, for CPU — according to the number of cores.

Laravel Horizon — Monitoring and Autoscaling

Installation: composer require laravel/horizon and php artisan horizon:install. config/horizon.php:

'environments' => [
    'production' => [
        'supervisor-1' => [
            'maxProcesses' => 10,
            'balanceMaxShift' => 1,
            'balanceCooldown' => 3,
            'queue' => ['critical', 'default', 'emails'],
            'balance' => 'auto',
            'minProcesses' => 1,
            'tries' => 3,
            'timeout' => 60,
        ],
    ],
],

Horizon automatically distributes workers across queues according to load. We tested: at a peak of 5000 tasks/min, Horizon handles twice as fast as ordinary queue:work without monitoring. Laravel Horizon

Tool Comparison

Failed Jobs

Failed tasks are saved and can be easily retried via php artisan queue:failed and php artisan queue:retry. We configure alerts in Telegram or Slack — the team knows about the problem instantly.

What Is Included in Queue Setup

• Designing the configuration for your project (number of queues, priorities);
• Installing and configuring Redis (or migrating from another broker);
• Creating Job classes with retry logic;
• Configuring Supervisor for production workers;
• Integrating Horizon with monitoring and alerts;
• Operational documentation and developer instructions;
• 2 weeks of support after delivery (guarantee of trouble-free operation).

Get a consultation on queue setup: we'll tell you how to double performance and forget about job loss. Order turnkey setup — from configuration to monitoring.

Estimated Timeframes

Basic setup — 1 working day. Adding Horizon and auto-scaling — another half day. Complex chains with integrations — 1–2 days. Contact us — we will evaluate your project in one hour and offer the optimal solution.

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.