planetscale-best-practices-matrix

From README

Best-practices matrix Purpose Map database findings to recommended PlanetScale features. Use this to ensure the assessment does not miss major safety and operational surfaces. Cross-engine recommendations Query Insights Recommend for every production database: Review slow, expensive, high-frequency, and erroring query patterns. For Postgres, sort Insights by CPU (sort=cpuTime on the Insights API) when diagnosing CPU pressure. For sharded Vitess, review vindex per query pattern and the trend after index or routing changes. Correlate regressions with deploys. Use tags/comments to map queries back to code. Use tag filtering/navigation in Query Insights: the tags API (insights/tags, insights/tags/summaries) on both engines, plus tag:key:value filtering and per-execution tag drill-down in the Vitess dashboard. Use anomalies as alert and automation inputs. Webhooks Recommend for operational events: Anomalies. Storage pressure. Branch readiness/sleeping. Primary promotion. Maintenance.