We are announcing the end-of-life (EOL) for the high availability (HA) model in Password Manager Pro that utilized RubyRep for database replication with PostgreSQL. This change is effective starting from Password Manager Pro build 13140.
Why RubyRep has been deprecated?
RubyRep has long served as a replication tool in our HA architecture starting from our initial HA model. However, as the RubyRep project has become stale and unmaintained for a prolonged period, posing increasing concerns over:
- Security vulnerabilities due to lack of patches
- Outdated jars with no latest version upgrades
- Compatibility issues with modern PostgreSQL versions
- Reliability risks from dormant and outdated dependencies
- SBOM (Software Bill of Materials) compliance challenges
Given the absence of recent updates or active development, we have made the decision to phase out RubyRep to ensure a more secure and sustainable HA model for Postgres database.
What's replacing RubyRep?
We are transitioning to PostgreSQL's native streaming replication, a modern solution that is:
- Natively supported and actively maintained by the PostgreSQL community
- Designed for high-performance and low-latency replication
- Fully compatible with the latest PostgreSQL tooling and ecosystems
- Capable of transparent failover and read-scaling
While RubyRep offered bi-directional replication, it was primarily used by our customers for failover, of which is now more efficiently handled by PostgreSQL's native features.
What does this mean for you?
The HA model with PostgreSQL is not being removed; it is being modernized and improved. Here is what you can expect:
- No disruption in functionality or loss of data consistency
- A more reliable and maintainable architecture
- Improved fault tolerance and system resilience
What are the actions required?
If you are currently using the old HA model with RubyRep, you will need to remove the existing configuration and follow our updated guide to set up the new PostgreSQL streaming replication-based HA model.
Note : If you choose to voluntarily continue using our existing HA model with RubyRep for database replication, whether due to business requirements or other constraints, we recommend reaching out to our support team for tailored guidance and assistance.
New HA architecture overview
The newly introduced HA architecture adopts a more robust and scalable approach, featuring active primary and secondary servers (read-write) connected to a shared PostgreSQL database, along with a supported read-only server. Data replication between servers is managed in real-time through PostgreSQL's native streaming replication, ensuring data consistency and service continuity.
This architecture is designed to deliver:
- High resilience against server or database failures
- Real-time data synchronization across all nodes
- Scalable performance with dual active primaries
- Uninterrupted service availability
Depending on your organizational needs, the following deployment models are supported:
- Primary and secondary servers with a shared database - Ideal for load balancing and managing primary instance failover
- Primary server with a read-only server - Suitable for backup servers or disaster recovery use cases. Enables read-scaling while keeping the primary secure and focused on write operations
- Primary and secondary servers with a shared database and an additional read-only server - Combines the benefits of load balancing, redundancy, and read-optimized access while ensuring high availability and scalability across all tiers
This new HA model is purpose-built to support mission-critical applications with zero downtime and optimal resource utilization.
Need help migrating?
Our documentation provides detailed steps to help you reconfigure your HA setup with PostgreSQL streaming replication. For any assistance, our support team is ready to guide you through the transition. By evolving our HA architecture, we are committed to delivering a more secure, performant platform for your organization's needs.