• Home

  • Custom Ecommerce
  • Application Development
  • Database Consulting
  • Cloud Hosting
  • Systems Integration
  • Legacy Business Systems
  • Security & Compliance
  • GIS

  • Expertise

  • About Us
  • Our Team
  • Clients
  • Blog
  • Careers

  • VisionPort

  • Contact
  • Expertise

    We have the experience and knowledge to choose the right tools.

    ‹ Return to Expertise Index

    Replication & Bucardo

    Quick Answer

    End Point Dev provides database replication solutions for PostgreSQL, MySQL, and SQL Server. Our consultants work with built-in features such as write-ahead log shipping, warm and hot standby, and streaming replication, along with third-party tools such as Bucardo. Replication can distribute read-only workloads, support multi-master configurations, move data into reporting systems, and form part of a backup and recovery strategy.

    Database Replication Solutions

    Database replication copies and maintains data or schema across multiple databases. The available approach depends on the database platform, application requirements, availability needs, and operating environment.

    PostgreSQL, MySQL, and SQL Server provide built-in replication capabilities. Third-party tools can add other options for data distribution, transformation, and multi-master configurations. Each approach has its own strengths and constraints. End Point Dev helps clients choose and implement a solution that balances cost, availability, performance, and operational complexity.

    Built-in Replication Features

    Common replication features include:

    • Write-ahead log shipping, which transfers recorded database changes to another system
    • Warm and hot standby configurations for failover and read-only workloads
    • Streaming replication for continuously sending changes to replicas

    Load Distribution With Replicas

    As demand grows, reporting jobs and other read-only activity can place added load on a primary database. Replicas can handle some of those workloads while the primary database continues to process application traffic. PostgreSQL hot standby and tools such as Bucardo and Slony can support different forms of load distribution.

    Multi-Master Replication

    Bucardo, developed by End Point Dev, supports two-way replication in which multiple databases can serve as authoritative repositories and exchange updates in near real time. This can support risk mitigation, lower latency for local services, or distribution across multiple data centers. Multi-master replication requires careful planning to manage conflicts and preserve data integrity.

    Backup and Recovery

    Replication can complement a database backup strategy. Depending on the workload, backups may be exported from a replica to reduce load on the primary system. End Point Dev also works with point-in-time recovery, filesystem snapshots, and other recovery approaches suited to the database and operating environment.

    Data Warehousing and ETL

    Complex reporting and analysis can consume substantial database resources. Moving selected data from production systems into a data warehouse can simplify reporting and reduce load on primary databases. Bucardo can support extraction, transformation, and loading workflows between databases.

    Replication Across Unreliable Connections

    Long distances, high latency, and intermittent connectivity can complicate replication. End Point Dev engineers design replication systems that account for these conditions while maintaining data consistency and recoverability.

    Frequently Asked Questions

    What types of databases can be replicated?

    End Point Dev works with replication for PostgreSQL, MySQL, and SQL Server, using built-in database features and third-party tools where appropriate.

    How can replication improve database performance?

    Replication can move reporting and other read-only workloads to replicas, reducing demand on the primary database. The result depends on the workload, database platform, and replication design.

    What is the difference between hot standby and warm standby?

    A warm standby maintains a recoverable copy that can take over after a failure. A hot standby also accepts read-only queries while receiving changes from the primary database.

    Key Takeaways

    • Database replication maintains copies of data across multiple database systems.
    • Built-in options include write-ahead log shipping, warm and hot standby, and streaming replication.
    • Replicas can support reporting, read-only workloads, failover, backups, and data warehousing.
    • Bucardo supports advanced use cases including data transformation and two-way multi-master replication.
    • Replication design should account for performance, availability, connectivity, recovery, and operational complexity.
    Send us a message!

    Related blog posts

    Bucardo 5.6.0 Released

    David Christensen · March 1, 2020

    Disaster Recovery — Miami to Dallas in one hit

    Ian Neilsen · October 3, 2017

    Throw It Away: Suppressing Writes on PostgreSQL Replicas

    Josh Williams · November 30, 2016

    Bucardo replication workarounds for extremely large Postgres updates

    Greg Sabino Mullane · May 31, 2016

    PostgreSQL Point-in-time Recovery: An Unexpected Journey

    David Christensen · January 15, 2016

    Odd pg_basebackup Connectivity Failures Over SSL

    Josh Williams · November 13, 2015