A cloud-native PostgreSQL manager providing high availability, leveraging streaming replication and cluster stores like etcd or Consul.
Stolon is a cloud-native PostgreSQL manager designed to deliver high availability for PostgreSQL databases in containerized environments like Kubernetes, as well as traditional infrastructures. It ensures data consistency while maximizing availability, making it suitable for production deployments where reliability is critical.
DevOps engineers and database administrators managing PostgreSQL clusters in Kubernetes or cloud environments, particularly those prioritizing data consistency and high availability.
Developers choose Stolon for its strong consistency guarantees during network partitions, seamless Kubernetes integration, and support for synchronous replication and point-in-time recovery, distinguishing it from simpler replication solutions.
PostgreSQL cloud native High Availability and more.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Prioritizes data consistency over availability in network partitions, preventing data loss by ensuring only consistent masters are elected, as highlighted in the project philosophy.
Provides seamless high availability within Kubernetes clusters with dedicated examples and documentation, making it ideal for containerized environments.
Supports both asynchronous and synchronous replication, allowing teams to balance performance with zero data loss guarantees, as detailed in the features.
Utilizes pg_rewind for quick resynchronization with the current master, minimizing downtime during failovers, as mentioned in the key features.
Enables multi-site replication and near-zero downtime migrations through standby clusters, documented in the project's features and documentation.
The project status warns that on-disk formats may change in future releases, potentially requiring complex upgrades or data migration, adding maintenance overhead.
Requires setting up and maintaining an external cluster store like etcd, Consul, or Kubernetes, which introduces additional infrastructure complexity and points of failure.
Involves multiple components (keeper, sentinel, proxy) that must be configured and monitored, increasing the learning curve and operational burden for teams.