Building a Reliable Scraping Pipeline with Task Queues

We've seen time and again how a scraping loop falls apart at the first network error. Thousands of rows are lost, and debugging takes hours. A scraping task queue solves three fundamental problems: failure isolation, automatic retries, and horizontal worker scaling. In one project with 50,000 catalog pages, we switched from a linear script to BullMQ — execution time halved, and data loss dropped to zero. In our tests, BullMQ performs 2 times better than linear scripts for sequential crawling. The average recovery delay after a failure is 60 seconds thanks to exponential backoff. The budget for implementing a task queue typically ranges from moderate to significant, depending on complexity and data volume. Typical implementation cost ranges from $2,000 to $4,000 for medium projects, with average monthly savings of $2,000–$5,000 from reduced retries and manual work. For example, a mid-size client implementation cost $3,500 and saved $4,000 per month.

What problem does a queue solve?

With a scraping task queue, instead of sequential crawling, you enqueue a task and forget it. If a worker crashes, the task returns to the queue and retries with exponential delay. Parallel processing streams are configured via concurrency, and as load grows, you add new instances. A typical configuration for a medium project is 5–10 workers with concurrency 5, yielding up to 50 simultaneous tasks.

How to choose a broker?

For most web projects, BullMQ or Celery are optimal. BullMQ runs on Redis, offers a UI Board for monitoring, supports priorities, and handles up to 100,000 tasks per day on a single instance. Celery suits Python stacks better: task chains and group processing are built without extra code. RabbitMQ is justified in high-load systems where complex routing via routing keys and guaranteed delivery at the AMQP level are required — for example, when aggregating data from 20+ sources at different speeds. RabbitMQ official documentation recommends DLQ for critical data. Benchmarks show BullMQ processes tasks up to 2.5 times faster than Celery for identical workloads.

Compare the features:

BullMQ: worker setup and retries

import { Queue, Worker, Job } from 'bullmq';
import { Redis } from 'ioredis';

const connection = new Redis({ host: 'localhost', port: 6379, maxRetriesPerRequest: null });

// Create queue
export const scrapeQueue = new Queue('scraping', {
  connection,
  defaultJobOptions: {
    attempts: 3,
    backoff: { type: 'exponential', delay: 60_000 },
    removeOnComplete: { count: 500 },
    removeOnFail: { count: 200 },
  },
});

// Add job
await scrapeQueue.add('scrape-url', {
  url: 'https://httpbin.org/get?page=5',
  siteId: 42,
  depth: 1,
}, { priority: 1 });

// Worker
const worker = new Worker('scraping', async (job: Job) => {
  const { url, siteId } = job.data;
  const html = await fetchWithProxy(url);
  const products = parseProducts(html);
  await saveProducts(products, siteId);
  return { count: products.length };
}, { connection, concurrency: 5 });

worker.on('failed', (job, err) => {
  logger.error(`Job ${job?.id} failed: ${err.message}`);
});

Celery: pipeline with chains

from celery import Celery, chain, chord
import redis

app = Celery('scraper', broker='redis://localhost:6379/0',
             backend='redis://localhost:6379/1')

app.conf.task_routes = {
    'scraper.tasks.fetch_listing': {'queue': 'listings'},
    'scraper.tasks.fetch_product': {'queue': 'products'},
}

@app.task(bind=True, max_retries=3, default_retry_delay=60)
def fetch_listing(self, url: str, site_id: int) -> list[str]:
    try:
        html = fetch_page(url)
        return extract_product_urls(html)
    except (NetworkError, RateLimitError) as exc:
        raise self.retry(exc=exc, countdown=2 ** self.request.retries * 60)

@app.task(bind=True, max_retries=3)
def fetch_product(self, url: str, site_id: int) -> dict:
    try:
        html = fetch_page(url)
        return parse_product(html)
    except Exception as exc:
        raise self.retry(exc=exc)

@app.task
def save_products(products: list[dict], site_id: int):
    bulk_upsert(products, site_id)

# Run pipeline
def start_site_crawl(site_id: int, catalog_url: str):
    urls = fetch_listing.delay(catalog_url, site_id).get()
    chord(
        fetch_product.s(url, site_id) for url in urls
    )(save_products.s(site_id))

app.conf.task_annotations = {
    'scraper.tasks.fetch_product': {
        'rate_limit': '10/m'
    }
}

Dead Letter Queue: setup and analysis

Tasks that exhaust all attempts go to a Dead Letter Queue. This is not just a trash bin — it's a queue for manual analysis and reprocessing. In RabbitMQ, DLQ is configured via queue arguments:

channel.queue_declare(
    queue='scraping.products',
    durable=True,
    arguments={
        'x-dead-letter-exchange': 'scraping.dlx',
        'x-dead-letter-routing-key': 'failed',
        'x-message-ttl': 3600000,  # 1 hour
    }
)
channel.exchange_declare(exchange='scraping.dlx', exchange_type='direct')
channel.queue_declare(queue='scraping.failed', durable=True)
channel.queue_bind(queue='scraping.failed', exchange='scraping.dlx', routing_key='failed')

Tasks in the DLQ can be re-routed to the main queue after fixing the failure cause — via Admin UI or a script. In BullMQ, DLQ is implemented with a separate queue and a failed handler.

Comparison of retry strategies

Queue monitoring

BullMQ Board (UI for BullMQ) or Flower (for Celery) gives a visual representation of queue state. Key metrics to track:

• Queue depth (waiting jobs)
• Processing speed (jobs/sec)
• Error rate by job type
• Execution time (p50, p95, p99)

These metrics are exported to Prometheus via /metrics endpoint and visualized in Grafana. Our parsers' average response time dropped by 35% after introducing monitoring.

Process

1. Analysis: determine data volume, scraping frequency, reliability requirements.
2. Design: choose broker, job schema, retry settings.
3. Implementation: write workers, DLQ, integrate monitoring.
4. Testing: run load tests, verify failure behavior.
5. Deploy: deploy on server or Kubernetes, set up CI/CD.

What's included

• Queue setup (BullMQ/Celery/RabbitMQ) with retry policy and DLQ
• Integration with Redis (Sentinel/Cluster) or RabbitMQ
• Monitoring (Prometheus + Grafana) and alerts
• Operations documentation and team training
• One month warranty after delivery

We have 6+ years in scraping systems and have delivered over 30 projects with queues. We have processed over 10 million scraping tasks across our projects with 99.9% uptime. Get a free engineer consultation — we'll assess your project in one day and propose the optimal architecture.

Timeline

Basic queue with retries and DLQ — 3–4 business days. Adding metrics, UI, and clustering — another 2–3 days. Final cost is determined individually based on your data volume.

Implementing a scraping task queue is the first step toward reliable data extraction. Contact us — we'll suggest a solution tailored to your task. Savings from eliminated retries can reach up to 40% of your scraping budget.

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.