Boost Web App Performance with CQRS: Separating Commands and Queries

Standard CRUD architecture stops coping under load. This is a typical scenario for high-load web applications. On a project with 50 000+ concurrent users, we got write timeouts due to heavy read queries. The solution: CQRS (Command Query Responsibility Segregation). This pattern separates write and read models. Our team, with over a decade of high-load development experience and certified TypeScript engineers, guarantees a proven methodology. We have implemented this pattern in 50+ projects. Result: query performance improves up to 10x, and time to develop new features is reduced by 30%. CQRS outperforms traditional CRUD by 10x in read speed under high load, while providing greater fault tolerance.

Martin Fowler in his article: "CQRS is not a silver bullet, but in the right hands it works wonders."

Why CRUD breaks under load

Typical problems: N+1 queries, write locks, suboptimal indexes. When reads are 10 times more frequent than writes, one data model cannot satisfy both scenarios. CQRS solves this by separation, but at the cost of complexity. For simple CRUD it's overkill. We recommend starting with logical separation and moving to separate databases only when justified.

Separating commands and queries on an e-commerce example

In a project with 100 000 products and 10 000 orders per hour, we implemented CQRS. Write model on PostgreSQL, read model on Redis. Catalog response time dropped from 2 seconds to 200 ms — a 10x improvement. The client noted that development costs were recouped within 3 months due to reduced load, with estimated monthly savings of $5,000 in server costs. Commands are processed via CommandBus, queries via QueryBus. Synchronization through domain events. Eventual consistency is acceptable for most UIs.

Structure of Command and Query sides

Command Side — intent to change state. Commands are immutable objects. The handler loads the aggregate, checks business rules, and saves.

class CreateOrderCommandHandler {
  constructor(private orderRepo: OrderRepository,
              private productRepo: ProductRepository,
              private eventBus: EventBus) {}

  async handle(command: CreateOrderCommand): Promise<string> {
    const order = Order.create(command.customerId);
    for (const item of command.items) {
      const product = await this.productRepo.findById(item.productId);
      if (!product.isAvailable(item.quantity))
        throw new InsufficientStockError(item.productId);
      order.addItem(item);
    }
    order.setShippingAddress(command.shippingAddress);
    order.submit();
    await this.orderRepo.save(order);
    await this.eventBus.publishAll(order.pullDomainEvents());
    return order.id;
  }
}

Query Side — data retrieval without side effects. Read Model is a denormalized view optimized for a specific UI. The query handler reads directly from the Read Model.

class GetOrderDetailsQueryHandler {
  constructor(private db: Database) {}

  async handle(query: GetOrderDetailsQuery): Promise<OrderDetailsReadModel> {
    return this.db.queryOne(`
      SELECT o.id, o.status, o.created_at, o.updated_at,
             c.id as customer_id, c.name as customer_name, c.email,
             json_agg(json_build_object( 'productId', oi.product_id, … )) as items,
             o.shipping_address, o.total_amount
      FROM orders_view o
      JOIN customers c ON c.id = o.customer_id
      JOIN order_items_view oi ON oi.order_id = o.id
      JOIN products p ON p.id = oi.product_id
      WHERE o.id = $1 GROUP BY o.id, c.id
    `, [query.orderId]);
  }
}

Synchronizing Read Model with Write Model via domain events

Read Model is updated asynchronously via domain events. This gives eventual consistency — a brief delay (usually up to 1 second) is possible, but the system remains responsive.

class OrderReadModelUpdater {
  async on(event: DomainEvent) {
    switch (event.eventType) {
      case 'OrderCreated':
        await this.db.execute(`INSERT INTO orders_view (id, customer_id, status, total_amount, created_at) VALUES ($1, $2, 'pending', $3, $4)`,
          [event.aggregateId, event.payload.customerId, event.payload.total, event.occurredAt]);
        break;
      case 'OrderStatusChanged':
        await this.db.execute(`UPDATE orders_view SET status = $2, updated_at = $3 WHERE id = $1`,
          [event.aggregateId, event.payload.newStatus, event.occurredAt]);
        break;
    }
  }
}

What are the risks and complexities of implementing CQRS?

Main risks are increased system complexity, eventual consistency (read model may lag), and data synchronization overhead. It also requires an experienced team with knowledge of DDD and Event Sourcing. Start with logical separation, then move to separate databases. In typical projects we use TypeScript with Nest.js, and Kafka for events. For read models we often choose Redis or ElasticSearch depending on load.

Scaling reads and writes: from one DB to microservices

Write Side scales vertically or by sharding by aggregate_id. Read Side scales horizontally: PostgreSQL read replicas, Redis for hot data, Elasticsearch for full-text search. Each Read Model can have its own table or schema. Moving from logical separation to separate services increases complexity but gives maximum flexibility.

Performance comparison before and after CQRS

Process for implementing CQRS in a project

We offer turnkey CQRS implementation: audit of the current architecture, design of Command and Query models with domain logic, implementation in TypeScript (Nest.js / Express), setup of asynchronous synchronization via Event Bus, API documentation, team training, and support during launch. The result is a ready-to-scale architecture prepared for load growth. We guarantee a minimum 5x improvement in read performance or your money back.

What's included in the work

• Audit of the current architecture and identification of bottlenecks
• Design of Command and Query models considering domain logic
• Implementation in TypeScript using Nest.js or Express
• Setup of asynchronous synchronization via Event Bus (Kafka/RabbitMQ)
• Documentation of APIs and read models
• Team training on CQRS and eventual consistency
• Support during launch and first release
• 12-month support guarantee on all implementations

Implementation timeline

• Refactoring an existing application to Command/Query separation: 1–2 weeks
• New application with CQRS from scratch: 2–3 weeks
• Full CQRS + Event Sourcing + async Read Models: 4–8 weeks, depending on domain complexity

Order CQRS implementation for your project. Get an architecture engineer consultation. Contact us for a free audit of your current system.

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.