citus

Distributed PostgreSQL as an extension (by hydradatabase)

Citus Alternatives

Similar projects and alternatives to citus

  • hydra

    Hydra: Column-oriented Postgres. Add scalable analytics to your project in minutes. (by hydradatabase)

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • hydra

    15 citus VS hydra

    Livecoding networked visuals in the browser (by hydra-synth)

  • hydra

    14 citus VS hydra

    Hydra is a framework for elegantly configuring complex applications (by facebookresearch)

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better citus alternative or higher similarity.

citus reviews and mentions

Posts with mentions or reviews of citus. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-09-19.
  • Show HN: Hydra - Open-Source Columnar Postgres
    6 projects | news.ycombinator.com | 19 Sep 2023
    Big congrats on 1.0! Super exciting project.

    My dream scenario would be installing hydra as an extension into my main rails application database. My usecase is showing analytics numbers directly to users, like "how many people visited my listing", which regular row-level postgres is not suited to answer. To do this now we need a to get that data from our DW, which is slow for single queries, so we need a cache, which we need to keep in sync, which is complexity I don't want. It would be amazing if I could do user-facing analytics queries directly in my main app db.

    What put me off after a quick scroll:

    Installing the extension changes the default table type to be columnar. I don't want an installed extension to do that, my main workload is still row oriented oltp, I only want specific tables to be columnar and I don't want to change all my normal migrations to specify `USING heap`. IMO timescale does this really well, it's an extension, not a new database. At least that's how I would want it to be.

    It also seems like you're trying to claim postgres foreign data wrappers as "hydra external tables", implying it's a new feature? Postgres does this (reading other databases and external files) out of the box and it feels sneaky to try and brand that.

    Also the FAQ says "Hydra is not a fork." When the engine clearly is: https://github.com/hydradatabase/citus I realize you want to monetize this as a bigger platform and that's completely fair, but it strikes me as dishonest to deny the citus originins in the FAQ.

Stats

Basic citus repo stats
1
2
10.0
over 1 year ago

hydradatabase/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.


Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com