Projects on cloudplz

No-Code Infrastructure Platform

Mon, 01 Jan 0001 00:00:00 +0000

The bottleneck in database infrastructure was never the databases — it was the queue in front of them. This platform removed the queue: product teams provision production-ready Aurora clusters through a web form, no Terraform required.

Challenge

Infrastructure as code made provisioning repeatable, but it traded one bottleneck for another:

Terraform expertise required. Not every team has it, and shouldn’t need it to get a database.
Lead times. A routine cluster request waited on the platform team’s queue.
Inconsistent patterns. Left to hand-write HCL, teams produced infrastructure that drifted in quality and shape.
The platform team as critical path. Every database request flowed through a small group — that doesn’t scale.

The goal: democratize provisioning without democratizing misconfiguration.

Aurora Migration Toolkit

Mon, 01 Jan 0001 00:00:00 +0000

Migrating a single database to Aurora is a project. Migrating fifty — including multi-terabyte, tier-0 systems with 24/7 write traffic — is a platform. This is the toolkit and methodology that made it repeatable.

Challenge

Each team’s database had different constraints: replication lag budgets, change-freeze windows, version skew between on-premises MySQL and Aurora, and applications that had grown assumptions about their database over a decade. One-off migration plans did not scale to fifty of them.

Terraform Module Library

Mon, 01 Jan 0001 00:00:00 +0000

Self-service infrastructure only works if the self-service path is the easiest path. This module library made the compliant, production-hardened way to provision AWS infrastructure also the fastest one.

Challenge

Seventy application repositories, each capable of provisioning its own infrastructure. Without a shared library, every team reinvents VPC wiring, database parameter tuning, and IAM boundaries — and every reinvention is a future incident and an audit finding.

Vitess Production Deployment

Mon, 01 Jan 0001 00:00:00 +0000

Running Vitess in production for three years teaches you where horizontal scaling actually bites: ops discipline, not demos. This is the record of what it took to run the system that powers YouTube’s MySQL fleet, at a scale far smaller than YouTube’s — and why that changes the calculus.

Challenge

A MySQL deployment outgrowing vertical scale: write volume and working set exceeding what a single well-tuned instance could absorb, with availability requirements that ruled out naive primary failover.

Database Canary Applications

Mon, 01 Jan 0001 00:00:00 +0000

When a platform team changes a Terraform module, bumps an engine version, or upgrades a connection library, the blast radius is every application built on top. Canary applications turn that blast radius into a tripwire.

Challenge

Platform-level changes fail in ways unit tests don’t catch: a parameter group default that breaks connection pooling, a provider upgrade that drifts state, an engine version with different driver behavior. The first signal used to be a product team’s pager.