conduit VS conduit-connector-postgres

I'd like to mention Conduit + its Postgres connector. The Pg connector comes built-in, so all that is needed is a single Conduit binary to get started. It relies on WAL, but the connector creates the replication slot itself (if needed).

GitHub - ConduitIO/Conduit: Data Integration for Production Data Stores. Conduit is meant to be a bit more general-purpose than Kafka Connect and is an easy drop-in replacement. We're working hard to make that even easier. We are still in the early stages of this project and are trying to build more and more connectors. You can find out more about our connector roadmap on the Github repo. Our connector philosophy is to be real-time first, and double down on change data capture (CDC) capabilities, all with permissive licensing.

If you're looking for a tool with a UI and in which you can also easily extend the functionality with your own, custom data connectors, you might also want take a look at Conduit which is another open-source tool we've developed to make building and running real-time data infrastructure more straightforward and less time consuming.

You might want to check out: https://github.com/conduitio/conduit

This is why we are working on a project called Conduit at Meroxa. We hope to change the experience software engineers have with data.

I'd like to mention Conduit + its Postgres connector. The Pg connector comes built-in, so all that is needed is a single Conduit binary to get started. It relies on WAL, but the connector creates the replication slot itself (if needed).