maxwell
connectors
| maxwell | connectors | |
|---|---|---|
| 6 | 3 | |
| 3,916 | 32 | |
| 0.4% | - | |
| 7.4 | 9.9 | |
| about 1 month ago | 1 day ago | |
| Java | Go | |
| 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.
maxwell
-
All the ways to capture changes in Postgres
we started using https://github.com/zendesk/maxwell its not perfect, e.g. its difficult to know who changed what, but we solved this by adding the the user performing the change to the mixin
-
similar bundle / approach to laravel-activitylog
You could consider some CDC software, which logs database queries (inserts, updates and deletes). For example maxwells daemon https://maxwells-daemon.io/
-
Best way to ETL the new rows in a table.
Or you could generate a Kafka queue from MariaDB directly with Maxwell.
- Zendesk to Be Acquired
-
CDC in Apache Airflow
Most of the solutions out there for doing CDC on MySQL involve using the transaction log. These include https://github.com/debezium/debezium , https://github.com/airbnb/SpinalTap, and https://github.com/zendesk/maxwell.
connectors
-
All the ways to capture changes in Postgres
No. We implemented our own [1] for a few reasons:
* Scaling well to multi-TB DBs without pinning the write-ahead log (potentially filling your DB's disk) while the backfill is happening. Instead, our connector constantly reads the WAL and works well in setups like Supabase that have very restrictive WAL sizes (1GB iirc).
* Incremental fault-tolerant backfills that can be stopped and resumed at will.
* Being able to offer "precise" captures which are logically consistent in terms of the sequence of create/update/delete events.
The last one becomes really interesting when paired with REPLICA IDENTITY FULL, because you can feed it into an incremental computation (perhaps differential dataflow) for streaming updates of a continuous computation.
Our work is based off of the Netflix DBLog paper, which we took and ran with.
[1] https://github.com/estuary/connectors/tree/main/source-postg...
-
Why would you ever not use CDC for ELT?
Our connectors themselves are fully OSS (for example, here's PostgreSQL)
-
What Is Dbt and Why Are Companies Using It?
We've used https://github.com/estuary/connectors/pkgs/container/source-... to load data sets in the many terabytes. Caveat that, while it's implemented to Airbyte's spec, we've only used it with Flow.
What are some alternatives?
debezium - Change data capture for a variety of databases. Please log issues at https://issues.redhat.com/browse/DBZ.
walex - Postgres change events (CDC) in Elixir
SpinalTap - Change Data Capture (CDC) service
temporal_tables - Temporal Tables PostgreSQL Extension
auditor-bundle - The missing audit log library
pg-event-proxy-example - Send NOTIFY and WAL events from PostgreSQL to upstream services (amqp / redis / mqtt)
tesla - The flexible HTTP client library for Elixir, with support for middleware and multiple adapters.
temporal_tables - Postgresql temporal_tables extension in PL/pgSQL, without the need for external c extension.
hackney - simple HTTP client in Erlang
talk-transcripts - Transcripts of Clojure-related talks
airbyte - The leading data integration platform for ETL / ELT data pipelines from APIs, databases & files to data warehouses, data lakes & data lakehouses. Both self-hosted and Cloud-hosted.