Database Migrations for Web Applications

Database Migrations for Web Applications

We build a database migration system that eliminates manual schema edits, lost changes, and deployment downtime. Instead of chaos with ALTER queries in chats and incidents due to code-database incompatibility—versioned scripts, automatic validation in CI/CD, and zero-downtime updates. Automated migrations reduce change approval time by 5x compared to manual requests. They also improve reliability and reduce incidents significantly. Automated migrations are 3x more reliable than manual schema changes.

Why Are Migrations Critical for Production?

Without migrations, teams often face schema drift between environments, data loss during manual ALTERs, and inability to roll back quickly. A configured migration system ensures the database always matches the code, and changes go through code review and testing. Over 90% of data-related incidents are caused by unverified schema changes—migrations eliminate this. With proper setup, over 95% of migrations execute without errors. The average rollback time for a failed migration is about 2 minutes.

How to Choose the Right Migration Tool?

Tool choice depends on the stack. We prefer universal solutions with pure SQL scripts, independent of ORM and runnable from CI without starting the application. For example, Flyway supports any stack and allows migrations via command line without Java environment if scripts are written in SQL.

Principles we follow:

• Each migration is atomic and reversible (down script required).
• Migrations in production are never edited—errors are fixed with new migrations.
• Data migrations are separate from schema migrations.

Example with golang-migrate

Create a migration to add a search vector:

migrate create -ext sql -dir db/migrations -seq add_search_vector_to_products

-- 000003_add_search_vector_to_products.up.sql
BEGIN;
ALTER TABLE products
    ADD COLUMN IF NOT EXISTS search_vector TSVECTOR;
UPDATE products
SET search_vector = to_tsvector('russian', coalesce(title, '') || ' ' || coalesce(description, ''));
CREATE INDEX CONCURRENTLY idx_products_search ON products USING GIN (search_vector);
CREATE OR REPLACE FUNCTION products_search_vector_update() RETURNS TRIGGER AS $$
BEGIN
    NEW.search_vector := to_tsvector('russian',
        coalesce(NEW.title, '') || ' ' || coalesce(NEW.description, '')
    );
    RETURN NEW;
END;
$$ LANGUAGE plpgsql;
CREATE TRIGGER products_search_vector_trigger
    BEFORE INSERT OR UPDATE ON products
    FOR EACH ROW EXECUTE FUNCTION products_search_vector_update();
COMMIT;

-- 000003_add_search_vector_to_products.down.sql
BEGIN;
DROP TRIGGER IF EXISTS products_search_vector_trigger ON products;
DROP FUNCTION IF EXISTS products_search_vector_update();
DROP INDEX IF EXISTS idx_products_search;
ALTER TABLE products DROP COLUMN IF EXISTS search_vector;
COMMIT;

Important: CREATE INDEX CONCURRENTLY cannot be executed inside a transaction. For such operations, use a separate step without BEGIN/COMMIT, or configure Flyway with executeInTransaction = false.

Zero-downtime Migrations

The golden rule: each migration must be compatible with both the previous and next code versions simultaneously. The deployment looks like this: migration is applied first, then new instances are brought up, old ones are gradually taken down—both generations run side by side.

-- Safe: NULL without DEFAULT
ALTER TABLE users ADD COLUMN phone VARCHAR(20);
-- Safe in PostgreSQL 11+: NOT NULL with DEFAULT (no table rewrite)
ALTER TABLE users ADD COLUMN is_verified BOOLEAN NOT NULL DEFAULT false;

How Migrations Reduce Incidents and Save Budget?

Systematic migrations reduce incidents by 3x compared to manual schema management. Thanks to automatic validation and code review, errors reach production 5x less often. This is confirmed by high-load projects where we implemented migrations.

What's Included in the Work

Project Phases

1. Analysis: study current schema, environments, deployment processes.
2. Design: choose tool, define naming conventions (timestamps).
3. Implementation: write initial migrations and templates for future ones.
4. Testing: verify on staging, simulate rollbacks.
5. Deployment: deploy with automatic validation.

Why Trust Us with Your Migrations?

Our team consists of engineers with over 5 years of experience in database administration and web application development. We have completed over 100 migration setup projects, including zero-downtime for high-load systems. We guarantee compatibility with any stack and transparent process documentation. We use certified tools—experience with golang-migrate, Flyway, Alembic, and others is confirmed by commercial projects.

Contact us for a free consultation—we will help you manage schema so that database changes stop being a headache. We will evaluate your project and propose the optimal solution. Order a current schema audit—we will find weak points and prepare a migration plan. Leave a request, and our engineer will contact you within a day.

Estimated timelines: setting up migration infrastructure for a new project—from half a day; reverse engineering an existing schema—1–2 days. Cost is calculated individually.

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.