Building a Production-Ready Image Processing Pipeline

Images are the heaviest part of any website. A single unprocessed camera photo can weigh 10+ MB and take seconds to load. Meanwhile, users abandon a page if LCP exceeds 2.5 seconds. We regularly encounter projects where images are not optimized: no resizing for different screens, no WebP, watermarks applied manually. All of this means lost conversions and wasted traffic costs.

A typical scenario: an e-commerce store with thousands of products. Photos are uploaded through the admin panel, but thumbnails have to be made manually or via workarounds. We offer a ready-made infrastructure: when a file is uploaded, it goes through a pipeline and immediately outputs several versions — thumbnail (150x150), medium (800x600), large (1920x1080) — all in WebP and JPEG. The original is also saved separately.

Watermarks are applied automatically if the image is public. We use a semi-transparent logo in the bottom-right corner — it doesn’t obstruct the view but protects the content. All operations take no more than 200 ms per image.

Our pipeline solves these problems automatically. You upload the original — the system itself generates a set of previews, converts to modern formats, and applies a watermark. And you don’t need to rewrite your existing logic: integration takes between 2 and 3 days. The pipeline can resize images automatically to needed dimensions, crop images exactly, and apply a watermark overlay.

What Problems Does the Pipeline Solve?

Slow loading due to large originals — first problem. One camera photo can weigh 20 MB. On mobile internet this destroys UX. Resizing to the required dimensions and conversion to WebP reduces size by 3–5 times without quality loss.

Lack of adaptive images — second problem. If you show a 1920x1080 image on desktop, on a phone it will be the same size but compressed by the browser, increasing LCP. Our pipeline generates several versions for different resolutions, and we set up srcset — the browser itself chooses the appropriate variant.

Inability to automatically convert formats — third problem. Manual conversion to WebP or AVIF is a slow process that is often forgotten. The pipeline does it on the fly, preserving both the original and the derivatives. Traffic savings reach 40%.

How We Build the Pipeline: Stack and Architecture

For synchronous processing we use Node.js with Sharp. Sharp is 3x faster than Python alternatives, according to Sharp library documentation. For asynchronous processing we use Celery + Pillow. If the load is high, we send tasks to a Redis queue — the server is not blocked. An alternative is imgproxy, which transforms images on-the-fly via URL.

Comparison of approaches:

Which to choose? If you have up to 1000 uploads per day — synchronous is enough. For large projects with millions of images — asynchronous with a queue, enabling batch image processing.

Comparison of formats:

Switching to WebP reduces LCP by 30% and saves up to 40% in traffic. Automatic format conversion (including WebP conversion) is built into the pipeline.

What’s Included in the Work?

The service includes:

• Architecture design of the pipeline (approach selection, stack).
• Development and integration with your project (API, middleware).
• CDN and caching setup (Cloudflare, Vercel) — we integrate a CDN for images to ensure fast delivery worldwide.
• Documentation for usage and further customization.
• Team training (1 hour online).
• 30-day support guarantee for stable operation.
• Access credentials and API keys.

Image optimization is part of the pipeline, reducing file sizes without quality loss.

Our team has 7+ years in web development and over 50 completed image processing projects. Our company has been on the market for over 5 years.

Work Process

1. Analysis — audit of current infrastructure, typical sizes, formats, load.
2. Design — choose approach (synchronous/asynchronous), define set of previews.
3. Implementation — write pipeline code, integrate with storage and CDN.
4. Testing — load testing, cross-browser compatibility checks.
5. Deployment — roll out to production with monitoring.

Timelines and Cost

A basic implementation with Sharp or imgproxy takes 2 to 5 days. Cost is calculated individually after an audit — it depends on complexity, volumes, and whether asynchronous processing is needed. We will assess your project for free within one day. Typical budgets start at $2,000 for a basic pipeline.

Typical Implementation Mistakes

• Ignoring EXIF orientation — photos from phones may be rotated. In Sharp we automatically read metadata and correct it.
• Loss of transparency — when converting PNG to JPEG, the background becomes white. Our pipeline preserves the alpha channel or replaces it with a white background.
• Too many preview sizes — generating 10+ variants slows down processing. Optimal is 3–4 sizes.
• No caching — every request to imgproxy consumes resources. We set Cache-Control to one year.

This image automation pipeline eliminates manual work and ensures consistent results.

# tasks.py (Celery)
from celery import Celery
from PIL import Image
import io, boto3

app = Celery('image_tasks', broker='redis://redis:6379')

@app.task(bind=True, max_retries=3)
def process_image(self, image_id: int):
    try:
        record = db.get_image(image_id)
        raw = s3.get_object(Bucket='uploads', Key=record.original_key)['Body'].read()
        img = Image.open(io.BytesIO(raw))
        img = ImageOps.exif_transpose(img)
        if img.mode == 'RGBA':
            background = Image.new('RGB', img.size, (255, 255, 255))
            background.paste(img, mask=img.split()[3])
            img = background
        variants = {}
        for name, (w, h) in SIZES.items():
            resized = img.copy()
            resized.thumbnail((w, h), Image.LANCZOS)
            buf = io.BytesIO()
            resized.save(buf, 'WEBP', quality=85, method=6)
            buf.seek(0)
            key = f"processed/{image_id}/{name}.webp"
            s3.put_object(Bucket='media', Key=key, Body=buf, ContentType='image/webp', CacheControl='public, max-age=31536000')
            variants[name] = key
        db.update_image_variants(image_id, variants)
    except Exception as exc:
        raise self.retry(exc=exc, countdown=60)

Get a consultation on your project — we’ll assess complexity and timelines. Write to us, we’re in touch.

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.