Working with Queues 📬

Offload slow tasks to background queues with Redis, RabbitMQ, and Beanstalk — handle emails, image processing, and notifications asynchronously.

What You'll Learn in This Lesson

• Why queues are essential for responsive web apps
• Build a job queue with push, process, retry, and fail
• Compare Redis, RabbitMQ, Beanstalk, and SQS
• Job lifecycle: pending → processing → completed/failed
• Run and manage worker processes with Supervisor

Note: PHP runs on a server. Our examples simulate PHP logic using JavaScript. To run real PHP, install PHP.

🎯 Real-World Analogy: A queue is like a restaurant kitchen ticket system. When a customer orders, the waiter (your app) puts a ticket on the rail (queue) and immediately goes back to serving. The kitchen (workers) processes tickets in order. If a dish fails, the chef retries it. If it keeps failing, it goes to the "problem" pile (dead letter queue) for the manager to review.

Queue Fundamentals

Without queues, your app blocks while sending emails, processing images, or calling external APIs — users wait seconds for a response. With queues, you push these slow tasks to a background worker and respond instantly. The worker processes jobs asynchronously, with automatic retries for failures.

Try It: Building a Queue

Push jobs, process them with retry logic, and track stats

Try it Yourself »

JavaScript

// Queue Fundamentals: Why Queues?
console.log("=== The Problem: Slow Synchronous Tasks ===");
console.log();
console.log("User registers → Your app does all of this BEFORE responding:");
console.log("  1. Insert user in DB .............. 50ms");
console.log("  2. Send welcome email ............. 2000ms 😱");
console.log("  3. Resize avatar .................. 1500ms 😱");
console.log("  4. Notify admin on Slack .......... 800ms 😱");
console.log("  Total: 4350ms — user waits 4+ seconds!");
conso
...

Message Brokers & Workers

Redis is the simplest queue backend — use LPUSH to add jobs and BRPOP to consume them. RabbitMQ adds advanced routing and guaranteed delivery. In production, run multiple worker processes managed by Supervisor for reliable, parallel processing.

Try It: Brokers & Workers

Compare Redis, RabbitMQ, and Beanstalk; manage workers with Supervisor

Try it Yourself »

JavaScript

// Message Brokers: Redis, RabbitMQ, Beanstalk
console.log("=== Message Broker Comparison ===");
console.log();
console.log("Broker       | Speed    | Persistence | Best For");
console.log("─────────────┼──────────┼─────────────┼──────────────────────");
console.log("Redis        | Fastest  | Optional    | Simple queues, caching + queues");
console.log("RabbitMQ     | Fast     | Yes         | Complex routing, enterprise");
console.log("Beanstalkd   | Fast     | Optional    | Lightweight job queu
...

⚠️ Common Mistakes

⚠️

No retry logic — external APIs fail temporarily. Always retry jobs 2-3 times with exponential backoff before marking them as failed.

⚠️

No dead letter queue — permanently failed jobs should go to a separate queue for manual inspection, not just disappear.

💡

Pro Tip: Use Laravel's built-in queue system for production — it handles retries, delays, rate limiting, and monitoring out of the box with Redis, SQS, or database backends.

📋 Quick Reference — Queues

Concept	Description
Producer	Your app — pushes jobs to the queue
Consumer/Worker	Background process that executes jobs
Broker	Redis, RabbitMQ, SQS — stores the queue
Dead Letter Queue	Stores permanently failed jobs
Supervisor	Process manager to keep workers running

🎉 Lesson Complete!

You can now build asynchronous PHP apps with queues! Next, learn to build email systems with SMTP, PHPMailer, and deliverability.