- rethinkdb_rebirth VS realtime
- rethinkdb_rebirth VS Hasura
- rethinkdb_rebirth VS flow
- rethinkdb_rebirth VS db_watch
- rethinkdb_rebirth VS timely-dataflow
- rethinkdb_rebirth VS noria
- rethinkdb_rebirth VS PipelineDB
- rethinkdb_rebirth VS cainophile
- rethinkdb_rebirth VS integrate
- rethinkdb_rebirth VS revori
Rethinkdb_rebirth Alternatives
Similar projects and alternatives to rethinkdb_rebirth
-
Hasura
Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
-
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.
-
flow
🌊 Continuously synchronize the systems where your data lives, to the systems where you _want_ it to live, with Estuary Flow. 🌊 (by estuary)
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
rethinkdb_rebirth reviews and mentions
-
Ask HN: Is there a way to subscribe to an SQL query for changes?
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
Stats
rethinkdb/rethinkdb_rebirth is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of rethinkdb_rebirth is C++.
Popular Comparisons
Sponsored