ksql
pg_ivm
| ksql | pg_ivm | |
|---|---|---|
| 4 | 19 | |
| 5,819 | 779 | |
| 0.4% | 2.8% | |
| 10.0 | 6.3 | |
| 5 days ago | about 1 month ago | |
| Java | C | |
| GNU General Public License v3.0 or later | 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.
ksql
- Supercharge your Kafka Clusters with Consumer Best Practices
- The Next Generation of Materialize
- PranaDB
-
Stream processing with sql and a nice gui? Alternatives to lenses.io?
Yeah, it’s community license — https://github.com/confluentinc/ksql/blob/master/LICENSE-ConfluentCommunity
pg_ivm
- Postgres is eating the database world
-
What Is Incremental View Maintenance (IVM)?
FTA, because I don't like Jeopardy questions in headlines:
“Incremental View Maintenance (IVM) provides a method for keeping materialized views current by calculating and applying only the incremental changes, as opposed to the complete recomputation of contents performed by the REFRESH MATERIALIZED VIEW command.”
Article shows using the pg_ivm Postgres extension available here: https://github.com/sraoss/pg_ivm
- Pg_ivm: Incremental View Maintenance as a Postgres Extension
- Anyone have experience with incremental materialized views in postgres?
- Incremental View Maintenance for PostgreSQL
-
a temporary-ish table vs materialize view?
There is an extension that provides some limited incremental MVIEW refresh: https://github.com/sraoss/pg_ivm
- Features I'd Like in PostgreSQL
- IVM (Incremental View Maintenance) Implementation as a PostgreSQL Extension
-
Materialized View: SQL Queries on Steroids
There’s awesome work being done on incremental view maintenance in postgres:
https://github.com/sraoss/pg_ivm
-
Should I replace all db select query REST APIs with a single generic router ?
It makes sense to perform managed denormalization - use a materialized view or automatically refresh a table or foreign server (via FDW) using common triggers (like pg_ivm does). And it's fine to add a TTL to it and use as a read store... update on user login and make a partial index just for that. And that's how you could get CQRS...
What are some alternatives?
kafka-connect-elasticsearch - Kafka Connect Elasticsearch connector
prawn-stack - A pageview counter using the AWS free tier, Postgres, Node and React
kpow-streams-agent - Monitor Kafka Streams applications with Kpow
materialize - The data warehouse for operational workloads.
risingwave - SQL stream processing, analytics, and management. PostgreSQL simplicity, unrivaled performance, and seamless elasticity. 🚀 10x more productive. 🚀 10x more cost-efficient.
pg_hint_plan - Extension adding support for optimizer hints in PostgreSQL
pranadb
contour - Contour is a Kubernetes ingress controller using Envoy proxy.
kafka-connect-file-pulse - 🔗 A multipurpose Kafka Connect connector that makes it easy to parse, transform and stream any file, in any format, into Apache Kafka
pg_jsonschema - PostgreSQL extension providing JSON Schema validation
debezium - Change data capture for a variety of databases. Please log issues at https://issues.redhat.com/browse/DBZ.
OpenLogReplicator - Open Source Oracle database CDC