PHP Laravel Backend Development: Optimization and Scaling

Problem: API slowness due to N+1 queries

You launch an e-commerce store on Laravel, and within a month the API starts to slow down: pages load in 3-4 seconds. The typical culprit is N+1 queries in Eloquent ORM. The frontend fetches a list of orders, each order pulls user and products — 100 queries instead of one. But that's just the tip of the iceberg: suboptimal migrations, missing cache, slow integrations. Let's break down how to design a backend that can handle growth.

Why Laravel solves N+1 queries

Laravel with Eloquent ORM provides built-in mechanisms: eager loading (with(), load()), caching (Redis, Memcached), query optimization through subqueries. We use Eloquent not as a simple ORM but as a tool to build efficient queries. For catalog with filters and pagination we apply dynamic scopes, for complex aggregations — subqueries. This reduces database load and speeds up responses. Compared to raw PHP, Laravel cuts development time by 2-3x thanks to ready-made solutions.

How we architect Laravel backends

Standard MVC is the base, but to support growth we add a service layer and repositories. Typical module structure:

app/
  Http/
    Controllers/
      Api/V1/
        ProductController.php
    Requests/
      CreateProductRequest.php
    Resources/
      ProductResource.php
    Middleware/
      EnsureRole.php
  Models/
    Product.php
  Services/
    ProductService.php
  Repositories/
    ProductRepository.php
  Jobs/
    SendOrderConfirmation.php
  Events/
    OrderPlaced.php

This approach isolates business logic from controllers and simplifies testing. We also use the Repository pattern to abstract database interaction. Unlike traditional MVC, the service layer allows easy replacement of implementations (e.g., switching from MySQL to PostgreSQL).

Typical backend bottlenecks in Laravel

Case study: tagged cache for e-commerce

For a store with 50,000 products we implemented tagged caching. Category data was cached for 5 minutes; when a product changed, only its category cache was invalidated. Catalog page load time dropped from 2 seconds to 200 ms. Redis as a cache server handles requests 10x faster than direct MySQL queries.

// Tagged cache
$products = Cache::tags(['products', "category:{$categoryId}"])
    ->remember("products:cat:{$categoryId}:page:{$page}", 300, function () use ($categoryId, $page) {
        return Product::active()->where('category_id', $categoryId)->paginate(20, ['*'], 'page', $page);
    });

Case study: async order processing

In another project we implemented queues for sending emails and generating PDFs. We used Laravel Queue with Redis driver. At a peak of 1000 orders per minute, the queue processed in 10 seconds. The retry algorithm with exponential backoff eliminated task loss. This solution allows scaling processing without increasing load on the main server.

How we test Laravel applications

Testing is a key stage. We write feature tests for API (PHPUnit), unit tests for services and repositories. Use Factory and Seeder for database seeding. On CI/CD we run tests before every deploy. This ensures changes don't break existing logic. This approach catches regressions early.

Process of work

1. Analysis: study requirements, load, current architecture.
2. Design: database schema, API structure, package selection.
3. Development: migrations, models, controllers, tests.
4. Integration: connect queues, cache, external services.
5. Deployment and monitoring: CI/CD setup, logging, alerts.

Estimated timelines

Exact timeline depends on complexity. Laravel provides powerful tools, but proper architecture is the key to success.

What's included in the work

• API documentation (OpenAPI/Swagger)
• Server and repository access
• Deployment instructions
• Team training (2-3 calls)
• 3-month warranty for bug fixes

Our team has over a decade of experience in Laravel and PHP, having implemented over 50 projects for e-commerce and enterprise systems. We guarantee stability and scalability.

Contact us for a free consultation and project evaluation.

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.