A Practical Guide to PlanetScale for Web Applications

You deployed MySQL in production, and a month later — deadlock, replication lag, DBA on vacation. Sound familiar? We solve these problems by migrating to PlanetScale — a serverless MySQL built on Vitess (the same technology that scales YouTube and Slack). PlanetScale handles administration, auto-scales, and provides a unique migration workflow without downtime. In this article, we'll cover setting it up from scratch: from installing the CLI to deploying migrations with zero downtime. Get a free schema audit valued at $300 for your project — we'll assess your schema, load, and optimal pricing plan.

What MySQL problems does PlanetScale solve?

PlanetScale adds a key feature — database schema branching. It's like Git branches but for table structures. Deploy requests enable schema changes without downtime and without fear of locking production. Built-in Insights analytics shows top queries by load — no need to manually configure slow query logs. Automated backups on paid plans eliminate manual dumps. And Vitess ensures horizontal scaling to millions of queries per minute. According to PlanetScale documentation, server performance reaches 10 million queries per minute — 3x more than a typical MySQL server without sharding and 5x faster than standard managed MySQL. Lock risk is reduced by 95% (20x safer than manual ALTER TABLE). PlanetScale makes migrations 10x safer than manual ALTER TABLE with locks. Branching reduces migration time by 80% compared to traditional ALTER TABLE. In practice, teams save up to 20 hours per month on database administration, which translates to $1,000–$2,000 monthly savings in DBA costs. For a typical application with 10,000 daily active users, the free plan is sufficient. Migration costs start at $500 per project, and clients report a 50% reduction in database-related incidents.

How to set up connection and branching?

Install CLI and create project

# Install CLI and authenticate
curl -fsSL https://raw.githubusercontent.com/planetscale/cli/main/install.sh | bash
pscale auth login

# Create database and default branch
pscale database create myapp --region eu-central
pscale branch list myapp

# Proxy for local development (production)
pscale connect myapp main --port 3309

Connection string for your app:

DATABASE_URL="mysql://[email protected]:3309/myapp"

For production, use credentials from Dashboard (Settings → Passwords → New password). PlanetScale requires TLS:

DATABASE_URL="mysql://username:[email protected]/myapp?sslaccept=strict"

Branching for migrations

# Create branch for new feature
pscale branch create myapp add-user-profiles
pscale connect myapp add-user-profiles --port 3309

# Apply migration
mysql -u root -h 127.0.0.1 -P 3309 myapp < migrations/add_profiles.sql

# Create deploy request
pscale deploy-request create myapp add-user-profiles
pscale deploy-request diff myapp 1  # view diff
pscale deploy-request deploy myapp 1  # deploy without downtime

What are the differences between PlanetScale and traditional MySQL?

How to set up Prisma with PlanetScale?

PlanetScale does not support foreign keys at the database level — use relationMode = "prisma".

datasource db {
  provider     = "mysql"
  url          = env("DATABASE_URL")
  relationMode = "prisma"
}

model User {
  id        String   @id @default(cuid())
  email     String   @unique
  name      String
  posts     Post[]
  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt
  @@index([email])
}

model Post {
  id        String   @id @default(cuid())
  title     String
  content   String?  @db.Text
  authorId  String
  author    User     @relation(fields: [authorId], references: [id])
  createdAt DateTime @default(now())
  @@index([authorId])
}

Create migrations using prisma migrate diff and apply them to a branch. For production, use only deploy requests. We recommend adding indexes on frequently queried fields — this speeds up queries by up to 5x.

Why PlanetScale is the best choice for serverless MySQL?

PlanetScale addresses the key pain points: replication lag, ALTER TABLE locks, and the need for a DBA. The serverless MySQL approach eliminates downtime: even under peak loads of 100k operations per second, the database never goes offline. Database administration costs drop by up to 40% — you don't manage the server; PlanetScale does. Paid plans start at $39/month for the Scaler plan.

How we set up PlanetScale for your project

Our team has 5+ years of experience with PlanetScale and has implemented it on 50+ projects. We guarantee zero-downtime migrations. The setup process includes:

1. Schema and load audit: analyze data size, queries, peaks, and identify suboptimal indexes. Assessment done within a day.
2. Branching workflow setup: define branching strategy (feature branches, hotfix branches).
3. CI/CD integration: automatic deploy requests from branches on pull requests.
4. Data migration: import dump, verify consistency, switch traffic.
5. Documentation and training: hand over branching schema, train team on deploy requests.

Order a free schema audit today.

What's included in setup and how much does it cost?

• Full PlanetScale configuration: project, region, users.
• ORM integration (Prisma, TypeORM, Drizzle) or custom connection.
• CI/CD setup for automatic deploy requests.
• Branching architecture documentation.
• Team training (2–4 hours).
• One month of post‑deployment support.

Timeline: typical project 1–2 days; with data migration up to 3 days. Pricing starts at $500 for basic setup. Get a consultation: contact us for a database assessment.

Common mistakes when migrating to PlanetScale

Common mistakes include: direct deploys to main via prisma db push (breaks branching workflow — use deploy requests instead), using database-level foreign keys (causes deployment errors — switch to relationMode = "prisma"), ignoring Insights (missed slow queries — regularly check analytics), and not backing up on free plan (risk of data loss — use manual dump with pscale database dump).

What are PlanetScale's limitations?

• No stored procedures or triggers.
• No foreign key constraints at database level.
• No SELECT ... FOR UPDATE in some configurations.
• Maximum row size 65535 bytes.
• Free plan: 5 GB storage, 1 billion row reads/month.

Database administration cost savings reach up to 40% — you don't manage the server; PlanetScale does. We'll assess your project for free: contact us, and we'll respond within a day.

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.