Deploying CockroachDB for Web Applications: Migration and Optimization

Your PostgreSQL cluster hits write limits, and manual sharding requires constant tweaks. For example, a SaaS platform with 50k users across different regions: data in one data center, high latency for remote clients. CockroachDB is a distributed SQL database that solves these problems without a single point of failure. As noted in the official documentation, UUID primary keys prevent hot spots and can boost performance by up to 95%. We have deployed CockroachDB on 30+ projects, from SaaS to global platforms. One client — a SaaS with 50k users — spent significant resources on a PostgreSQL cluster. After migrating to CockroachDB, costs decreased by approximately 40%, and fault tolerance reached 99.99%. Contact us for a free consultation — we will evaluate your project.

CockroachDB vs PostgreSQL: Key Differences

CockroachDB is a distributed SQL database compatible with the PostgreSQL protocol. Unlike PostgreSQL, it provides horizontal scaling — adding nodes increases write throughput. Automatic replication copies data to multiple nodes; a node failure does not affect operations. Multi-region deployment stores data in different regions, ensuring local data compliance. Under loads exceeding 10k queries per second, CockroachDB processes transactions 2–3 times faster than PostgreSQL with manual sharding. You continue using pg drivers and familiar SQL.

Why CockroachDB Is Better for Global Web Applications

Global applications require low latency in all regions. CockroachDB supports geo-partitioning: data is automatically placed closer to the user. This reduces response time and improves interface responsiveness. Additionally, built-in replication ensures data consistency during failures — no single point of failure. For SaaS platforms, this means stable performance even under peak loads.

How to Quickly Set Up a Dev Cluster?

For development, a single node without SSL is enough. Installation takes 10 minutes. Execute these steps:

1. Download and extract the binary:

   wget -qO - https://binaries.cockroachdb.com/cockroach-latest.linux-amd64.tgz | tar xz
   mv cockroach-*/cockroach /usr/local/bin/
   

2. Start a single-node cluster in the background:

   cockroach start-single-node --insecure --background --store=/var/lib/cockroachdb --listen-addr=localhost:26257 --http-addr=localhost:8080 --log-dir=/var/log/cockroachdb
   

3. Create a database and user:

   cockroach sql --insecure -e "CREATE DATABASE myapp; CREATE USER myapp WITH PASSWORD 'strong_password'; GRANT ALL ON DATABASE myapp TO myapp;"
   

The database is now available at localhost:26257, web interface at localhost:8080.

How to Configure a Production Cluster with Three Nodes?

On each node, generate certificates and start the process. Then initialize the cluster:

cockroach start \
  --certs-dir=/etc/cockroachdb/certs \
  --advertise-addr=10.0.0.1 \
  --join=10.0.0.1,10.0.0.2,10.0.0.3 \
  --store=/var/lib/cockroachdb \
  --background

cockroach init --certs-dir=/etc/cockroachdb/certs --host=10.0.0.1

The cost of operating a cluster depends on the chosen instances and region. In our experience, migration pays off by eliminating manual sharding.

How to Adapt the Schema?

Syntax is almost identical to PostgreSQL, but use UUID instead of SERIAL:

CREATE TABLE users (
    id          UUID PRIMARY KEY DEFAULT gen_random_uuid(),
    email       STRING NOT NULL UNIQUE,
    name        STRING NOT NULL,
    created_at  TIMESTAMPTZ NOT NULL DEFAULT now()
);

CREATE TABLE orders (
    id          UUID PRIMARY KEY DEFAULT gen_random_uuid(),
    user_id     UUID NOT NULL REFERENCES users(id),
    status      STRING NOT NULL DEFAULT 'pending',
    total       DECIMAL(10,2) NOT NULL,
    created_at  TIMESTAMPTZ NOT NULL DEFAULT now(),
    INDEX idx_orders_user (user_id, created_at DESC),
    INDEX idx_orders_status (status, created_at DESC)
);

How to Configure Multi-Region Deployment?

For global applications, enable geo-partitioning:

ALTER DATABASE myapp SET PRIMARY REGION 'eu-central-1';
ALTER DATABASE myapp ADD REGION 'us-east-1';
ALTER DATABASE myapp ADD REGION 'ap-southeast-1';

ALTER TABLE users SET LOCALITY REGIONAL BY ROW;

Each row is stored closer to the user — crdb_region is determined automatically.

How to Avoid Serialization Errors in CockroachDB?

CockroachDB uses optimistic locking, so under concurrent access you may encounter error 40001. Add retry logic with exponential backoff. Example in TypeScript using the pg driver:

import { Pool } from 'pg'

const pool = new Pool({
  connectionString: process.env.DATABASE_URL,
  max: 25,
  idleTimeoutMillis: 30000,
  connectionTimeoutMillis: 5000,
})

async function withRetry<T>(fn: () => Promise<T>, maxRetries = 3): Promise<T> {
  for (let attempt = 0; attempt < maxRetries; attempt++) {
    try {
      return await fn()
    } catch (err: any) {
      if (err.code === '40001' && attempt < maxRetries - 1) {
        const delay = Math.min(100 * Math.pow(2, attempt), 2000)
        await new Promise(r => setTimeout(r, delay + Math.random() * 100))
        continue
      }
      throw err
    }
  }
  throw new Error('max retries exceeded')
}

async function transferFunds(fromId: string, toId: string, amount: number) {
  return withRetry(async () => {
    const client = await pool.connect()
    try {
      await client.query('BEGIN')
      const { rows: [from] } = await client.query(
        'SELECT balance FROM accounts WHERE id = $1 FOR UPDATE', [fromId]
      )
      if (from.balance < amount) throw new Error('insufficient funds')
      await client.query('UPDATE accounts SET balance = balance - $1 WHERE id = $2', [amount, fromId])
      await client.query('UPDATE accounts SET balance = balance + $1 WHERE id = $2', [amount, toId])
      await client.query('COMMIT')
    } catch (e) {
      await client.query('ROLLBACK')
      throw e
    } finally {
      client.release()
    }
  })
}

Retry logic is critical. Proper implementation ensures transaction execution without data loss.

Common Mistakes When Implementing CockroachDB

• Using INTEGER IDs — creates hot spots. Replace with UUID.
• Missing retry logic — transactions will fail with error 40001.
• Incorrect region selection — delays for remote users.
• No monitoring — hard to track cluster performance.

Get a consultation for your project — we will evaluate the load and recommend a configuration.

What Is Included in the Work?

Estimated Timelines

We have been configuring distributed databases for over 5 years and have delivered 30+ projects on CockroachDB. We guarantee 99.99% fault tolerance and full post-deployment support. Contact us for a free consultation — we will evaluate your project and suggest the optimal solution. Order a database audit — we will select the best CockroachDB configuration for you.

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.