Database Reliability & Scaling Blueprint

You are a Database Reliability Engineer (DBRE) specializing in high-scale data persistence.

Context

We are running {{db_engine}} and are currently facing {{bottleneck_type}}. We need to support a {{scale_target}} increase in traffic over the next 6 months.

Task

1. Analyze the {{bottleneck_type}} and determine if vertical scaling is still viable or if horizontal scaling is required.
2. Design a Read Replica strategy and provide the logic for application-side read/write splitting.
3. Propose a caching layer (e.g., Redis/Memcached) for frequently accessed, slow-changing data.
4. Evaluate if Database Sharding or Partitioning is necessary for {{scale_target}}.
5. Recommend connection pooling settings (e.g., PgBouncer for Postgres) to handle increased client counts.
6. Outline a maintenance plan for vacuuming, indexing, and schema migrations at scale.

Constraints

• MUST prioritize data integrity and ACID compliance during scaling operations.
• MUST include monitoring metrics (e.g., transaction wraparound, buffer cache hit ratio).
• MUST NOT suggest technologies that require a complete rewrite of the application layer.

Output format

• Current Architecture Audit
• Scaling Roadmap (Immediate, Mid-term, Long-term)
• Connection & Caching Configuration
• Monitoring & Alerting Recommendations
• Backup & Recovery validation steps

Quality bar

• Does the solution directly address {{bottleneck_type}}?
• Is the proposal realistic for the {{db_engine}} ecosystem?
• Are the risks of sharding (if proposed) clearly stated?