Breaking up a monolith: How we’re unwinding a shared database at scale | Datadog

This post details Datadog's strategy and process for unwinding a large, shared PostgreSQL database into independently owned instances. It outlines the challenges of shared databases, the prerequisites for successful decomposition (platform investments like Rapid and OrgStore, and a PG Proxy for traffic shifting), and a three-phase migration plan: logical separation (identifying data domains via DBM query samples and team collaboration), access reduction, and physical separation. The post emphasizes the importance of defining clear data domain boundaries and ensuring teams have the necessary tooling and platform support to manage their own database instances safely and scalably.