MySQL/MariaDB Administration: Optimization, Replication, Backups

Full Lifecycle Administration of MySQL and MariaDB for Web Projects

Imagine: a WordPress site crashes with 1000 concurrent visitors, even though the server is powerful. Most likely, the issue is in MySQL—InnoDB buffer pool not configured, indexes missing on frequent queries, binary log filling the disk. Such scenarios are common: a typical project loses up to 30% performance due to suboptimal configuration. We solve these tasks daily, with over 50 successful projects in MySQL and MariaDB administration under our belt. We guarantee stable operation and a 20-50% performance boost after tuning.

Problems We Solve

Table fragmentation. MyISAM without regular OPTIMIZE slows down selects. InnoDB also fragments after frequent UPDATE/DELETE operations. The database size grows, performance drops. Slow queries. Missing indexes, N+1 queries in the application, suboptimal JOINs without keys. Replication. Setting up master-replica without lag control leads to desynchronization. Binary log overflow without rotation fills the entire disk—server stops. Load balancing. Without ProxySQL, reads and writes go to one server, creating a bottleneck.

How We Do It

Initial Audit

-- Assess state: database sizes, fragmentation, slow queries
SELECT table_schema,
       ROUND(SUM(data_length + index_length) / 1024 / 1024, 1) AS size_mb
FROM information_schema.tables
GROUP BY table_schema
ORDER BY size_mb DESC;

Then we analyze slow_query_log and config files. Based on the data, we select parameters. For example, for a 50 GB database with high write load, we increase innodb_log_file_size to 1 GB, reducing checkpoint time by 40%.

InnoDB Optimization

The key parameter is innodb_buffer_pool_size. For a dedicated server, we allocate 70-80% of RAM. We increase log file size to 512 MB—this reduces checkpoint frequency and speeds up writes. File per table (innodb_file_per_table = ON) simplifies backup and optimization. As a result, a typical 100 GB database gets a 30-60% query speed boost.

[mysqld]
innodb_buffer_pool_size = 4G
innodb_buffer_pool_instances = 4
innodb_log_file_size = 512M
innodb_log_buffer_size = 64M
innodb_flush_log_at_trx_commit = 1
innodb_file_per_table = ON
innodb_read_io_threads = 8
innodb_write_io_threads = 8
innodb_io_capacity = 2000
innodb_io_capacity_max = 4000

How We Optimize the Database: Step by Step

1. Audit current configuration and performance.
2. Analyze slow queries and indexes (we detect up to 90% of suboptimal queries).
3. Tune InnoDB parameters (buffer pool, log file, IO threads).
4. Set up master-replica replication with lag control (target lag < 1 sec).
5. Configure automatic backups (mysqldump for small databases, XtraBackup for large ones).
6. Implement monitoring and alerts (Prometheus + Grafana, ProxySQL for load balancing).
7. Document configuration and train your administrator.

Why Replication Matters

Master-replica replication provides fault tolerance: if the master fails, we switch to the replica. We configure it so that lag does not exceed 1 second. We use ROW-format binary log—it is safer than STATEMENT for applications with stored procedures. Example configuration:

-- On master
CREATE USER 'replication'@'%' IDENTIFIED BY 'strong_password';
GRANT REPLICATION SLAVE ON *.* TO 'replication'@'%';
SHOW MASTER STATUS;

-- On replica
CHANGE MASTER TO
  MASTER_HOST = '10.0.0.1',
  MASTER_USER = 'replication',
  MASTER_PASSWORD = 'strong_password',
  MASTER_LOG_FILE = 'mysql-bin.000001',
  MASTER_LOG_POS = 12345;
START SLAVE;

Backups: mysqldump vs XtraBackup

For databases up to 10 GB, we use mysqldump with --single-transaction—backup without locking InnoDB. For large databases, we use Percona XtraBackup: it physically copies data, works up to 3 times faster, and barely loads the server. Both methods are automated with rotation and integrity checks.

# mysqldump for small databases
mysqldump --single-transaction --quick --routines --triggers --flush-logs -u backup -p mydb | gzip > /backups/mydb_$(date +%Y%m%d).sql.gz

# XtraBackup for large databases
xtrabackup --backup --user=backup --target-dir=/backups/full_$(date +%Y%m%d)

Backup Method Comparison

Optimization and Monitoring

We regularly defragment tables using OPTIMIZE TABLE or pt-online-schema-change (without locking). Monitoring via performance_schema: we track top slow queries and locks. We set up alerts when disk usage exceeds 80%.

What to Do When Binary Log Grows

Binary log grows if rotation is not configured. Set expire_logs_days = 7 in my.cnf, and regularly run PURGE BINARY LOGS BEFORE NOW() - INTERVAL 7 DAY. For replication, use ROW format: it is more compact under mixed load. Log size can be controlled with alerts—when disk reaches 80%, a notification triggers.

[mysqld]
expire_logs_days = 7
max_binlog_size = 500M
binlog_format = ROW

Estimated Work Timelines

Timelines depend on complexity: audit takes 1-2 days, configuration tuning 2-3 days, replication setup 1-2 days, backup setup 1 day. Full cycle—from 5 to 10 working days. Cost is calculated individually and pays off by reducing server load by up to 40%. Order a primary audit—we will show real growth points.

What’s Included

• Audit of current configuration and performance (with a report).
• InnoDB tuning for workload (optimize buffer pool, log file, IO).
• Master-replica replication setup with lag monitoring.
• Automatic backup configuration (mysqldump/XtraBackup) with rotation.
• Monitoring integration (performance_schema, disk and lag alerts).
• Documentation on configuration and recovery procedures.
• Training for your administrator (2-3 hours of consultations).
• 1 month warranty support after implementation.

Contact us for a primary audit of your database. Order MySQL/MariaDB tuning and forget about performance issues. Our team guarantees results: stable operation without surprises.

For additional information, refer to InnoDB documentation and Wikipedia on replication.

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.