A high-availability PostgreSQL cluster with automatic failover and cluster recovery.
Yoke is a PostgreSQL high-availability cluster solution that provides automatic failover and automated cluster recovery. It ensures database continuity by managing a three-node cluster (primary, secondary, monitor) and handling node failures without manual intervention. The project simplifies PostgreSQL redundancy management, reducing downtime and administrative effort.
Database administrators and DevOps engineers managing PostgreSQL deployments that require high availability and minimal downtime. It is suited for teams needing automated failover solutions without complex commercial tools.
Developers choose Yoke for its simplicity, automation, and open-source approach to PostgreSQL high availability. It offers a lightweight, self-hosted alternative to proprietary clustering solutions, with built-in recovery mechanisms and clear role-based configuration.
Postgres high-availability cluster with auto-failover and automated cluster recovery.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Detects primary node failures and promotes the secondary automatically, minimizing downtime without manual intervention, as per the automatic failover feature in the README.
Uses clear primary, secondary, and monitor roles defined in config.ini files, making cluster management intuitive and reducing configuration errors.
Provides a free, self-hosted alternative to commercial HA solutions under the MPL 2.0 license, eliminating licensing fees for PostgreSQL redundancy.
Automatically recovers the cluster to a healthy state after failures or network partitions, ensuring continuous availability without admin recovery steps, as highlighted in the key features.
Requires SSH key configuration without passwords and rsync installation on all nodes, increasing deployment complexity and potential for errors, as noted in the requirements.
Lacks built-in support for external monitoring tools; status introspection is confined to the basic yokeadm CLI, with documentation primarily on godoc offering limited operational guidance.
Relies on rsync for data synchronization, which can be slow and inefficient for large databases, impacting failover performance due to potential latency during data transfer.