rethinkdb_rebirth VS pg-live-select

Compare rethinkdb_rebirth vs pg-live-select and see what are their differences.

rethinkdb_rebirth

The open-source database for the realtime web. (by rethinkdb)

pg-live-select

Live Updating PostgreSQL SELECT statements (by numtel)
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.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
rethinkdb_rebirth pg-live-select
1 1
1,016 56
- -
0.0 0.0
over 5 years ago about 6 years ago
C++ JavaScript
GNU General Public License v3.0 or later GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

rethinkdb_rebirth

Posts with mentions or reviews of rethinkdb_rebirth. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-04-22.
  • Ask HN: Is there a way to subscribe to an SQL query for changes?
    17 projects | news.ycombinator.com | 22 Apr 2021
    I know [RethinkDB][1] used to do this with their SQL-like ReQL language, but I looked around a bit and can't find much else about it - and I would have thought it would be more common.

    If we think about modern frontends using SQL-based backends, essentially every time we render, its ultimately the result of a tree of SQL queries (queries depend on results of other queries) running in the backend. Our frontend app state is just a tree of materialized views of our database which depend on each other. We've got a bunch of state management libraries that deal with trees but they don't fit so well with relational/graph-like data.

    I came across a Postgres proposal for [Incremental View Maintenance][2] which generates a diff against an existing query with the purpose of updating a materialized view. Oracle also has [`FAST REFRESH`](https://docs.oracle.com/database/121/DWHSG/refresh.htm#DWHSG8361) for materialized views.

    I guess it's relatively easy to do until you start needing joins or traversing graphs/hierarchies - which is why its maybe avoided.

    [1]: https://github.com/rethinkdb/rethinkdb_rebirth

pg-live-select

Posts with mentions or reviews of pg-live-select. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-04-22.

What are some alternatives?

When comparing rethinkdb_rebirth and pg-live-select you can also consider the following projects:

realtime - Broadcast, Presence, and Postgres Changes via WebSockets

PipelineDB - High-performance time-series aggregation for PostgreSQL

Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.

db_watch

flow - 🌊 Continuously synchronize the systems where your data lives, to the systems where you _want_ it to live, with Estuary Flow. 🌊

revori - A revision-oriented DBMS

timely-dataflow - A modular implementation of timely dataflow in Rust

noria - Fast web applications through dynamic, partially-stateful dataflow