Investigate real-time replication of PostgreSQL clusters for DR purposes
- Dominant language
- Shell
- Stars
- 2
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
As part of migrating services to the GOLD cluster, we need to investigate real-time replication options for the PostgreSQL clusters used in Wallets.
Critical services must remain highly available, with near-instant failover to a replica in the event of a DR scenario, without data loss or corruption. This likely requires both primary and standby clusters to operate in an active state with real-time replication.
We are currently using the CrunchyDB Operator, which is also available on the GOLD cluster. However, CrunchyDB supports leader/follower HA but does not provide multi-master real-time streaming replication.
The platform also offers the EnterpriseDB Operator (requires commercial license). EnterpriseDB supports real-time multi-master (BDR) replication, where read/write operations occur on both clusters simultaneously. In an active/active setup, if one cluster fails, applications continue to function without interruption.
This investigation should evaluate the feasibility of using EnterpriseDB for Wallet workloads, including licensing, conflict resolution, operational complexity, and alignment with BC Gov DR requirements.
Contributor guide
Assessment
This issue has not been assessed yet.