Geo is built on top of PG streaming replication, but it isn't a hard requirement. Geo could be built on top of PG replication generally. Given that Cells cannot use PG streaming replication, this is an opportunity for Geo to become more flexible to serve many more use-cases. Possible configurations to unlock: * Cells: Organization Mover may use PG logical replication and Geo (with modifications). * Geo with PG logical replication * Geo with Amazon/Google DMS * Geo for non-PG data, but the secondary site uses the primary PG DB Known issues (not an exhaustive list) to resolve (create issues for these under this epic): * `rake gitlab:geo:check` complains if you don't have PG streaming replication set up * **Admin Area \> Geo \> Sites** shows unhealthy secondary site if you don't have PG streaming replication set up * Geo's measurement of DB replication lag in the codebase may only be applicable to PG streaming replication ### Participants - `@dbalexandre` - `@mkozono` - `@s_murray` - `@nsilva5` <!-- STATUS NOTE START --> ## Status 2025-03-04 This epic has been closed, so shouldn't be picking it up anymore. _Copied from https://gitlab.com/groups/gitlab-org/-/epics/13721#note_2376952296_ <!-- STATUS NOTE END -->