Managed Databases Rules | BeforeMerge

Pricing Blog Contributors Install Guide

Explore
Managed Databases

Managed Databases

v1.0.0

Review rules and best practices for popular hosted database platforms including connection pooling, backups, and scaling.

11 rules

3 categories

Performance(4)

Configure Connection Pooling

Serverless and edge environments exhaust database connections without a pooler. Use PgBouncer, Supavisor, or platform-native pooling.

supabaseconnection-poolingNeon

Architecture(4)

Verify Backup and Recovery Configuration

Every hosted database should have point-in-time recovery (PITR) enabled and tested.

supabaseBackup & RecoveryAmazon RDS

Security(3)

Require TLS/SSL on all database connections

Enforce sslmode=require (or stricter, with CA verification) so no client can connect to the managed database over plaintext.

Grant least-privilege roles; never let apps use superuser

Create scoped application roles with only the privileges they need; reserve superuser/owner accounts for migrations and admin.

Rotate database credentials regularly and never share them

Issue per-service credentials from a secrets manager, rotate them on a schedule, and keep them out of source control.

Automate Managed Databases checks on every PR

BeforeMerge scans your pull requests against all 11 Managed Databases rules automatically. Get actionable feedback before code ships.

Join Waitlist Browse All Rules

AI-native code review knowledge base. Structured rules that catch what linters miss.

Product

Features
Explore
Pricing
Docs
GitHub

Company

About
Blog
Contributors
Contributing

Legal

Privacy Policy
Terms of Service
MIT License

© 2026 BeforeMerge. Built by

Set statement and idle-in-transaction timeouts

Configure statement_timeout and idle_in_transaction_session_timeout so stuck queries and orphaned transactions are killed automatically.

MEDIUM

Monitor connection-limit usage and slow queries

Track connection count against max_connections and capture slow queries (e.g. via pg_stat_statements) with alerting thresholds.

Right-size the instance and monitor CPU, IO, and storage

Match instance class and storage to actual load, and alert on CPU, IOPS, and free-storage thresholds before they are hit.

Use Database Branching for Migrations

Test migrations on a branch/copy before applying to production. Neon and PlanetScale have native branching.

Migration SafetyNeonPlanetScale

HIGH

Offload read traffic to read replicas where appropriate

Route read-heavy or analytics queries to read replicas, keeping the primary focused on writes and consistency-critical reads.

Design for failover and high availability

Use a multi-AZ/standby configuration and ensure the app reconnects cleanly on failover instead of caching a dead endpoint.

Features Explore

Rules Skills Knowledge Prompts

Pricing Blog Contributors Install Guide

Hosted Database Review

Platform-specific review skill covering best practices for managed database services.

Platforms Covered

Supabase — PostgreSQL with RLS, Auth, Realtime
Neon — Serverless PostgreSQL with branching
PlanetScale — MySQL-compatible with branching
Amazon RDS / Aurora — Managed PostgreSQL and MySQL
Google Cloud SQL — Managed PostgreSQL, MySQL, SQL Server
Azure Database — Managed PostgreSQL and MySQL
CockroachDB — Distributed SQL
Turso / libSQL — Edge SQLite

Review Areas

Connection pooling configuration
Backup and recovery strategies
Scaling and read replicas
Security and access control
Cost optimization
Migration strategies between providers