pghoard VS Modify

• Multi-cloud object storage support
  pghoard supports backing up to multiple cloud storage providers including AWS S3, Google Cloud Storage, Azure Blob Storage, Swift, and local filesystem, giving flexibility in choosing or switching backup destinations.
• Streaming WAL archiving and compression
  It supports continuous WAL streaming and archiving with built-in compression (using algorithms like Snappy, LZMA, or zstd) and encryption, reducing storage costs and improving backup transfer efficiency.
• Point-in-time recovery (PITR)
  pghoard enables point-in-time recovery by combining base backups with WAL segments, allowing restoration of a PostgreSQL database to any specific moment, which is critical for disaster recovery scenarios.
• Open source and actively maintained by Aiven
  Being maintained by Aiven, a company specializing in managed database services, pghoard benefits from real-world production use, ongoing updates, and community contributions, ensuring reliability and continued support.
• REST API and monitoring integration
  It provides a REST API for managing and monitoring backup operations, and can integrate with monitoring systems, making it easier to automate backup workflows and track backup health in production environments.

Possible disadvantages

• PostgreSQL-specific tool
  pghoard is designed exclusively for PostgreSQL, so organizations using multiple database systems would need separate backup solutions for other databases, increasing operational complexity.
• Complex initial setup and configuration
  Setting up pghoard requires careful configuration of cloud storage credentials, encryption keys, and WAL-G-like settings, which can be complex for users unfamiliar with PostgreSQL internals or cloud storage APIs.
• Limited GUI or dashboard
  pghoard primarily operates via command-line and configuration files with a basic REST API, lacking a polished web-based dashboard for easier visualization and management compared to some commercial backup solutions.
• Documentation gaps for edge cases
  While basic documentation exists, users have reported that some advanced use cases, troubleshooting steps, and edge-case scenarios are not thoroughly documented, requiring deeper investigation into the source code.
• Smaller community compared to alternatives
  Compared to more widely adopted tools like pgBackRest or Barman, pghoard has a smaller user community and fewer third-party resources, tutorials, or plugins, which may limit support options for troubleshooting.

• No-code website modifications
  Modify allows users to make changes to their websites without needing to write code, making it accessible for non-developers who want to customize their web presence quickly.
• Easy A/B testing and personalization
  The platform enables users to run A/B tests and personalize website content for different audiences without requiring developer involvement, speeding up optimization efforts.
• Quick deployment
  Changes can be deployed rapidly through Modify's interface, bypassing the traditional development cycle and reducing time-to-market for website updates and experiments.
• Visual editor
  Modify provides a visual editor that lets users point-and-click to make changes on their site, making it intuitive and reducing the learning curve for new users.
• No impact on site codebase
  Since modifications are applied as an overlay rather than directly changing the source code, the original codebase remains clean and unaffected, reducing the risk of breaking existing functionality.

Possible disadvantages

• Limited awareness and community
  Modify is a relatively niche tool with a smaller user base compared to established competitors like Google Optimize or Optimizely, which means fewer community resources, tutorials, and third-party integrations.
• Performance concerns
  Applying modifications via a third-party script layer can introduce additional page load time or cause flickering effects as changes are rendered on top of the original page content.
• Limited customization depth
  While the no-code approach is convenient for simple changes, more complex modifications or deeply integrated features may still require developer intervention, limiting what can be achieved through the platform alone.
• Dependency on third-party service
  Relying on Modify means your website changes are dependent on their service uptime and continuity. If the service goes down or shuts down, applied modifications could be lost.
• Potential SEO implications
  Client-side modifications applied via JavaScript overlays may not be fully recognized by search engine crawlers, which could lead to discrepancies between what users see and what gets indexed.

• Pgbackrest is no longer being maintained

  The "closest" would be using Barman with hook scripts (https://docs.pgbarman.org/release/3.18.0/user_guide/hook_scripts.html#hook-scripts-using-barman-cloud-scripts-as-hooks-in-barman) if you rely on cloud storage for storing backups.... - Source: Hacker News / 6 months ago

• Future PostgreSQL: improvement to the replication protocol

  This story starts with our own PgHoard, a PITR backup tool for PostgreSQL. PgHoard offers several methods to archive the WAL (Write Ahead Log), including pg_receivewal, a small application shipping with PostgreSQL which connects to a... - Source: dev.to / almost 5 years ago

Tracking Modify since Mar 2021.