## Problem to solve To improve scalability the GitLab database team [split the backend database into two separate databases](https://gitlab.com/groups/gitlab-org/-/epics/6168). Geo currently built to work with a single backend database. In order to support the future state of GitLab deployments, Geo needs to support the decomposed two database model that is currently running on GitLab.com. This is related to the of [Decomposition: Support for self-managed customers](https://gitlab.com/groups/gitlab-org/-/epics/7509) effort. ## Intended users * [Sydney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) * [Ingrid (Infrastructure Operator)](https://about.gitlab.com/handbook/product/personas/#ingrid-infrastructure-operator) ## Proposal Identify and bridge the gaps to supporting multiple backend databases on Geo. ## Testing - Testing should ensure zero data loss under DR scenarios once the multiple backend database support is implemented. - Geo should be re-enabled on staging-ref once staging-ref updated to use multiple backend databases so that regular testing of Geo in this environment is restored. ## What does success look like, and how can we measure that? - Successful transition to the multiple backend databases with minimal disruption to our customers, delivered via a GitLab update. - No data is loss during or after the upgrade. - Minimal support cases resulting from said upgrade. ## What is the type of buyer? * Premium * Ultimate