Software Catalogue - Clustering/replication

Bi-Directional Replication (BDR) is an asynchronous multi-master replication system for PostgreSQL, specifically designed to allow geographically distributed clusters. Supporting up to 48 nodes (and possibly more in future releases) BDR is a low overhead, low maintenance technology for distributed databases.

Multi-master and multi-slave asynchronous replication system for Postgres.

CloudNativePG is an open source operator designed to manage PostgreSQL workloads on any supported Kubernetes cluster running in private, public, hybrid, or multi-cloud environments. CloudNativePG adheres to DevOps principles and concepts such as declarative configuration and immutable infrastructure.

It defines a new Kubernetes resource called Cluster representing a PostgreSQL cluster made up of a single primary and an optional number of replicas that co-exist in a chosen Kubernetes namespace for High Availability and offloading of read-only queries.

Applications that reside in the same Kubernetes cluster can access the PostgreSQL database using a service which is solely managed by the operator, without having to worry about changes of the primary role following a failover or a switchover. Applications that reside outside the Kubernetes cluster, need to configure a Service or Ingress object to expose the Postgres via TCP. Web applications can take advantage of the native connection pooler based on PgBouncer.

CloudNativePG was originally built by EDB, then released open source under Apache License 2.0 and submitted for CNCF Sandbox in April 2022. The source code repository is in Github.

Tungsten Enterprise is a complete replication and data management solution for PostgreSQL. Tungsten Enterprise uses replication and distributed management to create virtualized databases using redundant data copies. Tungsten Enterprise helps customers build fault-tolerant clusters that ensure uninterrupted access to data, improve performance and lower costs. Best of all, Tungsten does not require DBMS upgrades, or application updates to use. It works transparently with existing applications and database versions.

Tungsten Enterprise builds on Tungsten Replicator, an open source, data replication engine for PostgreSQL. Tungsten Enterprise includes distributed management with simple operator commands to view status and perform maintenance, business rules to execute failover procedures, transparent SQL routing and load balancing, and integration with high-end storage systems like NetApp. Tungsten Enterprise runs equally well in clouds as well as on local hardware.

Tungsten Enterprise customers include large enterprises, SaaS businesses, social networking sites and ISPs. Applications that depend on Tungsten Enterprise range from in-house IT systems to multi-tenant applications that process hundreds of millions of transactions a day for thousands of customers.

EDB Postgres for Kubernetes is an operator designed, developed, and supported by EDB that covers the full lifecycle of a highly available Postgres database clusters with a primary/standby architecture, using native streaming replication. It is based on the open source CloudNativePG operator, and provides additional value such as compatibility with Oracle using EDB Postgres Advanced Server and additional supported platforms such as IBM Power and OpenShift.

Key features available include: - Kubernetes API integration for high availability - Self-healing through failover and automated recreation of replicas - Capacity management with scale up/down capabilities - Planned switchovers for scheduled maintenance - Read-only and read-write Kubernetes services definitions - Rolling updates for Postgres minor versions and operator upgrades - Continuous backup and point-in-time recovery - Connection Pooling with PgBouncer - Integrated metrics exporter out of the box - PostgreSQL replication across multiple Kubernetes clusters - Red Hat certified operator for OpenShift

The operator has been renamed from Cloud Native PostgreSQL. Existing users of Cloud Native PostgreSQL will not experience any change, as the underlying components and resources have not changed.

GridSQL is a shared-nothing clustered database system targeted at data warehousing and data mart applications. It includes intelligence to maximize parallelization over multiple servers, delivering faster query response times than can be achieved by single-node databases.

Kubegres is a Kubernetes operator allowing to deploy a cluster of PostgreSql instances with data replication enabled out-of-the box. It brings simplicity when using PostgreSql considering how complex managing stateful-set's life-cycle and data replication could be with Kubernetes.

Kubegres has the following features:

• It creates a cluster of PostgreSql servers with data replication enabled: it creates a Primary PostgreSql pod and a number of Replica PostgreSql pods and replicates primary's database in real-time to Replica pods.

• It manages fail-over: if a Primary PostgreSql crashes, it automatically promotes a Replica PostgreSql as a Primary.

• It has a data backup option allowing to dump PostgreSql data regularly in a given volume.

• It provides a very simple YAML with properties specialised for PostgreSql.

• It is resilient, has over 55 automatized tests cases and has been running in production.

• It works with the PostgreSql containers created by the Docker Official Images team: it does not ship nor require a custom Docker image to work.

Kubegres was developed by Reactive Tech Limited and Alex Arica as the lead developer.

It was developed with the framework Kubebuilder version 3, an SDK for building Kubernetes APIs using CRDs. Kubebuilder is maintained by the official Kubernetes API Machinery Special Interest Group (SIG).

You can find more details about how to install and use it in the Getting started page

Pervasync Database Synchronization Framework supports synchronization of local PostgreSQL databases with central PosrgreSQL databases.

The signature feature of the framework is that it allows you to sub-set the central server data using free form SQL queries with parameters. Each local database could sync shared as well as private data with central databases.

Synchronization could be two-way, meaning writes can be done on both local and central databases. Change capture, conflict detection and resolution are built in to the core of the sync framework.

pg_auto_failover is an extension and service for PostgreSQL that monitors and manages automated failover for a Postgres cluster. It is optimized for simplicity and correctness and supports Postgres 10 and newer.

pg_auto_failover supports several Postgres architectures and implements a safe automated failover for your Postgres service. It is possible to get started with only two data nodes which will be given the roles of primary and secondary by the monitor. Starting with pg_auto_failover version 1.4, it is possible to implement a production architecture with any number of Postgres nodes, for better data availability guarantees.

The pg auto failover documentation is available online at https://pg-auto-failover.readthedocs.io/ and includes a fully detailed tutorial to get started using Azure VMs.

Pg Chameleon is a MySQL to PostgreSQL replica system developed in python 3.3+. The system can replicate the data changes from MySQL to PostgreSQL in real time.

The library python-mysql-replication collects the data changes fromt the mysql replication protocol and use PostgreSQL as relay log and as replica destination.

Home page

Pypi package

Github page

pglogical is a logical replication system implemented entirely as a PostgreSQL extension. Fully integrated, it requires no triggers or external programs. This alternative to physical replication is a highly efficient method of replicating data using a publish/subscribe model for selective replication.

Pgpool-II is a synchronous replication system for PostgreSQL 7.4 or later.It provides all desired functionalities to build a high performance/high availabilty cluster using PostgreSQL, including connection pooling and load balancing.

Pgpool can also be integrated with other replication systems such as Slony-I.

Postgres-XL is a massively parallel database built on top of, and very closely compatible with PostgreSQL 9.5. It is different because it supports both Business Intelligence workloads and high-volume transactional write and read workloads all on the same platform. It is designed to be horizontally scalable and flexible enough to handle various workloads including:

• OLTP write-intensive workloads
• Business Intelligence requiring OLAP with MPP parallelism
• Operational data store
• Key-value store including JSON
• GIS Geospatial
• Mixed-workload environments

repmgr handles setup and management of read-only replicas of a database. It works using replication features including with PostgreSQL, starting with version 9.0. The program includes a command line tool that can manage the cluster from a single node, as well as a background daemon to assist in monitoring and node failover.

Slony-I is a "master to multiple slaves" replication system supporting cascading (e.g. - a node can feed another node which feeds another node...) and failover.

The big picture for the development of Slony-I is that it is a master-slave replication system that includes all features and capabilities needed to replicate large databases to a reasonably limited number of slave systems.

Slony-I is a system designed for use at data centers and backup sites, where the normal mode of operation is that all nodes are available.

SteelEye LifeKeeper and SteelEye Data Replication (SDR) are field proven business continuity solutions that provide high-availability and data replication for systems hosting either PostgreSQL or EnterpriseDB’s Postgres Plus. Because of the mission-critical nature of the data managed in these environments a fundamental requirement is to have the ability to detect problems that impact the availability of that information and failover the processing to a standby server. Both servers may be on the same LAN, connected across the WAN, and can be hosted on either a physical or virtual machines. This flexibility allows for the easy configuration and provisioning of these systems while assuring users continue to be productive and in touch with the information they need. Protect your deployment from the everyday challenges we face in today’s business environment. For more information about SteelEye’s family of business continuity solutions, visit us at http://www.steeleye.com.

We have released TCapture release version 0.9

TCapture is a Replication Server Multi master solution for "PostgreSQL" databases

the Engine is a combination of java, custom decoder lib, custom _rdb_bdr schema moving the data replication and slots/publication/subsctiption configuration on "PostgreSQL" side. The data decoded from wals is moved in primary nodes tables (walq_node tables) which are published. The node joininig a primary node flow replication subscribe the walq primary node table and scan the walq to apply the replicate data locally.

Replication slots are created on primary nodes for : main decoderer slot each subscriptor node of its walq publication

The java engine ( RepSrvr ) duty is to move data from decoder wal to walq table in a robust, secure, fast, reliable manner. The java engine (Consumer) duty is to scan the walq locally tables and apply changes to local databases managing filters and conflicts.

There are two separate github repository available:

tcrespsrv development edition
tcrespsrv enterprise edition

both share the main architecture concepts, but differ in the implementation and have been published separately. In particular they differ in the modules regarding transactions capture and apply, sequential for the dev edition, multithreaded for the enterprise version

Please see the [repository] See (https://www.tcapture.net/) and GitHub development edition and GitHub enterprise edition.

Please feel free to use and send us any inquiry/idea about our project to: (mktg(dot)tcapture(at)gmail(dot)com) (mktg(dot)tcapture(at)gmail(dot)com) (TCapture active Committer)

xDB Replication Server provides replication from Oracle or Microsoft SQL Server to PostgreSQL all managed from a robust and easy to use graphical user interface. xDB features a distributed multi-publication/subscription architecture that allows you to synchronize data across geographies utilizing a snapshot or continuous replication modes. Other features include selective table replication, row filtering, a replication scheduler, cascading replication, a history viewer, and the ability to work in either graphical or CLI environments. You can save your organization time and money with replication by offloading reporting loads to a second server for better overall read/write performance, seeding new databases with data, or migrating data off old systems to PostgreSQL.