StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Databases
  4. Database Tools
  5. Citus vs Galera Cluster

Citus vs Galera Cluster

OverviewComparisonAlternatives

Overview

Galera Cluster
Galera Cluster
Stacks54
Followers102
Votes0
Citus
Citus
Stacks60
Followers124
Votes11
GitHub Stars12.0K
Forks736

Citus vs Galera Cluster: What are the differences?

Introduction

Citus and Galera Cluster are both database clustering solutions that aim to improve performance and scalability of database systems. However, there are key differences between the two.

  1. Data Distribution: In Citus, data is sharded and distributed across multiple machines, allowing for parallel processing and improved performance. On the other hand, Galera Cluster uses a multi-master replication model, where data is replicated across all nodes in the cluster, providing high availability and consistency.

  2. Write Scalability: Citus provides horizontal write scalability by distributing writes across shards, allowing for high write throughput. Galera Cluster, on the other hand, distributes write requests through a synchronous replication mechanism, limiting write scalability to a certain extent.

  3. High Availability: Citus relies on sharding and replication to provide high availability. If a shard or node fails, the data can still be accessed from other shards or nodes. In Galera Cluster, every node has a complete copy of the database, allowing for automatic failover and high availability.

  4. Schema Changes: Citus supports distributed schema changes, allowing for seamless schema modifications across shards. Galera Cluster, however, requires all nodes to make the same schema changes at the same time, which can be more challenging and time-consuming.

  5. Transaction Isolation: In Citus, transaction isolation is maintained within each shard, and distributed transactions are not supported out of the box. On the other hand, Galera Cluster supports distributed transactions with full ACID guarantees, ensuring consistency across multiple nodes in the cluster.

  6. Compatibility: Citus is an extension on top of PostgreSQL and is fully compatible with PostgreSQL, providing access to a wide range of PostgreSQL features. Galera Cluster is built on top of MySQL and is fully compatible with MySQL, allowing for seamless integration with MySQL applications and tools.

In summary, Citus excels in horizontal write scalability, high availability through sharding and replication, and compatibility with PostgreSQL, while Galera Cluster offers high availability through node replication, distributed transactions, and seamless integration with MySQL applications.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

Galera Cluster
Galera Cluster
Citus
Citus

It’s an easy-to-use, high-availability solution, which provides high system up-time, no data loss and scalability for future growth. You can Keep it up and running 24/7. Putting our expertise to use will help you avoid trial and error.

It's an extension to Postgres that distributes data and queries in a cluster of multiple machines. Its query engine parallelizes incoming SQL queries across these servers to enable human real-time (less than a second) responses on large datasets.

True Multi-master Read and write to any node at any time; Synchronous Replication No slave lag, no data is lost at node crash; Tightly Coupled All nodes hold the same state; Multi-threaded Slave For better performance.
Multi-Node Scalable PostgreSQL;Built-in Replication and High Availability;Real-time Reads/Writes On Multiple Nodes;Multi-core Parallel Processing of Queries;Tenant isolation
Statistics
GitHub Stars
-
GitHub Stars
12.0K
GitHub Forks
-
GitHub Forks
736
Stacks
54
Stacks
60
Followers
102
Followers
124
Votes
0
Votes
11
Pros & Cons
No community feedback yet
Pros
  • 6
    Multi-core Parallel Processing
  • 3
    Drop-in PostgreSQL replacement
  • 2
    Distributed with Auto-Sharding
Integrations
MongoDB
MongoDB
PostgreSQL
PostgreSQL
Oracle
Oracle
MySQL
MySQL
SQLFlow
SQLFlow
MariaDB
MariaDB
.NET
.NET
Apache Spark
Apache Spark
Loggly
Loggly
Java
Java
Rails
Rails
Datadog
Datadog
Logentries
Logentries
Heroku
Heroku
Papertrail
Papertrail
PostgreSQL
PostgreSQL

What are some alternatives to Galera Cluster, Citus?

MongoDB

MongoDB

MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.

MySQL

MySQL

The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.

PostgreSQL

PostgreSQL

PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.

dbForge Studio for MySQL

dbForge Studio for MySQL

It is the universal MySQL and MariaDB client for database management, administration and development. With the help of this intelligent MySQL client the work with data and code has become easier and more convenient. This tool provides utilities to compare, synchronize, and backup MySQL databases with scheduling, and gives possibility to analyze and report MySQL tables data.

Microsoft SQL Server

Microsoft SQL Server

Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

SQLite

SQLite

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.

Cassandra

Cassandra

Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

Memcached

Memcached

Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

MariaDB

MariaDB

Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

dbForge Studio for Oracle

dbForge Studio for Oracle

It is a powerful integrated development environment (IDE) which helps Oracle SQL developers to increase PL/SQL coding speed, provides versatile data editing tools for managing in-database and external data.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase