PostgreSQL Connection Pooling: Part 4 – PgBouncer vs Pgpool-II

In our previous posts in this series, we spoke at length about using PgBouncer and Pgpool-II, the connection pool architecture and pros and cons of leveraging one for your PostgreSQL deployment. In our final post, we will put them head-to-head in a detailed feature comparison and compare the results of PgBouncer vs. Pgpool-II performance for your PostgreSQL hosting!

PostgreSQL Connection Pooling Series

How Do the Features Stack Up?

Let’s start by comparing PgBouncer vs. Pgpool-II features:

Follower Clusters — 3 Major Use Cases for Syncing SQL and NoSQL Deployments

Follower clusters are a ScaleGrid feature that allows you to keep two independent database systems (of the same type) in sync. Unlike cloning or replication, this allows you to maintain an active, point-in-time copy of your production data. 

This extra cluster, known as a follower cluster, can be leveraged for multiple use cases, including for analyzing, optimizing and testing your application performance for MongoDB, MySQL, and PostgreSQL. In this article, we will cover the top three scenarios to leverage follower clusters for your application.