SaaSHub helps you find the best software and product alternatives Learn more →
Citus Alternatives
Similar projects and alternatives to citus
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
Hasura
Blazing fast, instant realtime GraphQL APIs on all your data with fine grained access control, also trigger webhooks on database events.
-
-
neon
Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.
-
-
cockroach
CockroachDB — the cloud native, distributed SQL database designed for high availability, effortless scale, and control over data placement.
-
TimescaleDB
An open-source time-series SQL database optimized for fast ingest and complex queries. Packaged as a PostgreSQL extension.
-
-
-
-
postgres-operator
Production PostgreSQL for Kubernetes, from high availability Postgres clusters to full-scale database-as-a-service. (by CrunchyData)
-
hydra
Hydra: Column-oriented Postgres. Add scalable analytics to your project in minutes. (by hydradatabase)
-
-
Greenplum
Discontinued Greenplum Database - Massively Parallel PostgreSQL for Analytics. An open-source massively parallel data platform for analytics, machine learning and AI.
-
-
-
-
citus discussion
citus reviews and mentions
- PostgreSQL Is the Database Management System of the Year 2024
-
PostgreSQL Meets ScyllaDB's Lightning Speed and Monstrous Scalability
This is just vanilla Postgres.
To start with I wonder how ScyllaDB will compare against Postgres extended with AGPL-licensed Citus [1]
Note: Like Github, Citus Data has been a subsidiary of Microsoft for a while now.
[1] https://www.citusdata.com/
-
Amazon Aurora DSQL
> FK constraints obviously dont work across system boundaries.
Not to their full extent, but they can still be used. At the simplest level, it is of course entirely possible to give different services their own schema in a given database, and FK constraints are supported across schemata in both MySQL and Postgres. Vertical scaling can take you enormously far with properly architected schemata and queries.
A more flexible, but still easy to reason about way to accomplish this is to have local versions of certain tables in each DB. This can be manually implemented (though this is not an easy problem to solve, for a variety of reasons), or by using something like Citus [0], which accomplishes this using 2PC. This is of course slower, but if your data model is carefully designed, it can be managed.
> soft deletes.
Sure, but now you have a new problem - needing to add a `is_deleted` or `deleted_at` column to a bunch of tables, and indexing that column on every table. In Postgres you might get away with this by using `DEFAULT [FALSE, NULL]` (respectively), and then creating a partial index with `...WHERE IS NOT [FALSE, NULL]`; that way the index size stays reasonable, and the cardinality isn't as horrible (well, it is for bools, but since you're only using it as a filter, it can work OK). Also, of course, you have to include this predicate in most queries.
> Its theoretical protection, not practically needed IMHO.
Different subjective experiences, of course, but IME it very much saves you time and headaches.
[0]: https://www.citusdata.com
-
CockroachDB License Change
Citus would be great if the HA story was better: https://github.com/citusdata/citus/issues/7602
- Show HN: Serverless Postgres
- SPQR 1.3.0: a production-ready system for horizontal scaling of PostgreSQL
- Citus: PostgreSQL extension that transforms Postgres into a distributed database
-
Figma's Databases team lived to tell the scale
I see they don't mention Citus (https://github.com/citusdata/citus), which is already a fairly mature native Postgres extension. From the details given in the article, in sounds like they just reimplemented it.
I wonder if they were unaware of it or disregarded it for a reason —I currently am in a similar situation as the one described in the blog, trying to shard a massive Postgres DB.
-
PostgreSQL Is Enough
It is possible, if you pay for it. You can do Multi-AZ Clustered Instances in RDS, where you get the benefits of Multi-AZ failover with traffic sharing.
If you can run your own infra – at least on an EC2 level – you can do things like Citus [0] for Postgres, which is about as close to "just add database nodes" as you'll get.
[0]: https://www.citusdata.com/
-
Vitess 18
So while searching for something like this for postgres I came across citus. Any one know how that stacks up?
https://github.com/citusdata/citus
-
A note from our sponsor - SaaSHub
www.saashub.com | 16 Jan 2025
Stats
citusdata/citus is an open source project licensed under GNU Affero General Public License v3.0 which is an OSI approved license.
The primary programming language of citus is C.