integrate
rethinkdb_rebirth
| integrate | rethinkdb_rebirth | |
|---|---|---|
| 1 | 1 | |
| 25 | 1,016 | |
| - | - | |
| 2.7 | 0.0 | |
| over 3 years ago | over 5 years ago | |
| Elixir | C++ | |
| MIT License | GNU General Public License v3.0 or later |
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.
integrate
-
Ask HN: Is there a way to subscribe to an SQL query for changes?
https://github.com/integratedb/integrate/blob/main/lib/integ...
These approaches rely on acking the WAL to confirm data has been processed. It’s simpler than running Debezium / Kafka for “zookept” CDC. However, they are “at least once” at best and it’s easy to shoot yourself in the foot so think twice before relying on this kind of thing for a real application.
Materialize is nice — TAIL is a lovely abstraction and their data ingest uses Debezium under the hood. That said, I believe their Postgres binlog source is still alpha / under active community dev.
rethinkdb_rebirth
-
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
What are some alternatives?
db_watch
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.
noria - Fast web applications through dynamic, partially-stateful dataflow
flow - 🌊 Continuously synchronize the systems where your data lives, to the systems where you _want_ it to live, with Estuary Flow. 🌊
timely-dataflow - A modular implementation of timely dataflow in Rust
cainophile
GRDB.swift - A toolkit for SQLite databases, with a focus on application development