# Database Canary Applications

> Customer-zero canary applications across seven data technologies — platform changes get validated on real connections before product teams ever see them.

---

LLMS index: [llms.txt](/llms.txt)

---

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.

What was needed:

- **Early detection** of breaking changes, before customer impact
- **Realistic testing** against real database connections, not mocks
- **Coverage** across every technology the platform supports
- **Automation** wired into the release pipeline, not run by hand

## Approach

A suite of applications, one per supported technology, that connect to real
clusters and execute representative operations continuously:

| Technology | Operations Exercised |
|------------|----------------------|
| Aurora MySQL | CRUD queries, transactions |
| Aurora PostgreSQL | CRUD queries, connection pooling |
| MongoDB Atlas | Document operations, aggregations |
| ElastiCache Redis | Caching, pub/sub |
| Kafka | Produce, consume |
| Elasticsearch | Index, search, aggregations |
| RabbitMQ | Queue, consume |

The applications run in QA and production environments and alert on failure
— so a broken module version announces itself in the canary before it
announces itself in a customer's incident channel.

Everything is provisioned through the platform's own no-code modules — the
canaries are the platform team's customer zero. Credentials live in a secrets
store, database users are dynamically provisioned, TLS enforced, IAM
authentication where supported. Secure-by-default isn't documented; it's how
the canaries themselves are built.

## Result

Seven technologies covered. Module releases, engine upgrades, and provider
changes are gated on canary validation instead of optimism. The application
patterns — secrets handling, tagging, monitoring wiring — became the
documented reference for product teams building on the platform.

The less obvious win: canaries made the platform team's own upgrades
routine. An engine version bump goes from "coordinated change with rollback
plan" to "canary passed, ship it."