connectors
walex
connectors | walex | |
---|---|---|
3 | 17 | |
33 | 256 | |
- | - | |
9.9 | 9.1 | |
2 days ago | 9 days ago | |
Go | Elixir | |
GNU General Public License v3.0 or later | MIT License |
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.
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.
walex
-
The Guide to PostgreSQL Data Change Tracking
The WAL CDC approach: https://github.com/cpursley/walex?tab=readme-ov-file#publica...
CREATE PUBLICATION news_item FOR TABLE news WHERE (topic IS "AAPL");
-
Elixir Nitpicks
What do you mean testing with processes?
I won't suggest these are the best written tests, but I test various processes, supervisors, etc like this:
https://github.com/cpursley/walex/blob/master/test/walex/sup...
-
PostgreSQL Is Enough
You don’t send the entire WAL, just what you subscribe to - and you can even filter via SQL: https://github.com/cpursley/walex?tab=readme-ov-file#publica...
- A Technical Dive into PostgreSQL's replication mechanisms
-
Fly Postgres, Managed by Supabase
What we do is much if the business logic in Postgres. But then there’s all the other stuff like external integrations, etc.
We handled that by having an Even system built on the Postgres WAL that we use like a callback system.
I put together a little library in Elixir (that originally started out as forked Supabase realtime) for this:
https://github.com/cpursley/walex
Recently added the ability to configure WalEx to forward events to webhooks or EventRelay (so you don’t need to know Elixir).
-
All the ways to capture changes in Postgres
If you're using Elixir, check out https://github.com/cpursley/walex
I've actually been thinking about turning this idea into a product where you can just point it at your postgres database and select the tables you want to listen to (with filters, like you describe). And have that forwarded to a webhook (with possibility of other protocols).
I'd love to hear folks thoughts on that (and if it would be something people would pay for).
-
Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps
Neat, this is the pattern I've been thinking about for a while now. Also glad to see this is Elixir based.
I've been using https://github.com/cpursley/walex (basically a fork of cainophile via a fork for subabase) to listen to Postgres changes in Elixir.
-
How to Listen to Database Changes Using Postgres Triggers in Elixir
https://github.com/cpursley/walex
Which is based on WAL logs and doesnt have the same limitations.
-
PostgreSQL Logical Replication Gotchas
Great writeup, just added this to the WalEx readme:
https://github.com/cpursley/walex
(WalEx is an Elixir lib for listening to the WAL and perform callback-like actions with the data)
-
We used Elixir's Observer to hunt down bottlenecks
Very cool.
I'm using Elixir to listen to change events via https://github.com/cpursley/walex (which I basically ripped off from Supabase).
What are some alternatives?
temporal_tables - Temporal Tables PostgreSQL Extension
PolarDB-for-PostgreSQL - A cloud-native database based on PostgreSQL developed by Alibaba Cloud.
pg-event-proxy-example - Send NOTIFY and WAL events from PostgreSQL to upstream services (amqp / redis / mqtt)
neon - Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, branching, and bottomless storage.
temporal_tables - Postgresql temporal_tables extension in PL/pgSQL, without the need for external c extension.
realtime - Broadcast, Presence, and Postgres Changes via WebSockets
maxwell - Maxwell's daemon, a mysql-to-json kafka producer
libcluster - Automatic cluster formation/healing for Elixir applications
debezium - Change data capture for a variety of databases. Please log issues at https://issues.redhat.com/browse/DBZ.
worker - High performance Node.js/PostgreSQL job queue (also suitable for getting jobs generated by PostgreSQL triggers/functions out into a different work queue)
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.
helm-charts - neondatabase helm charts