kafka-connect-jdbc

Kafka Connect connector for JDBC-compatible databases (by confluentinc)

Kafka-connect-jdbc Alternatives

Similar projects and alternatives to kafka-connect-jdbc

  1. kafdrop

    Kafka Web UI

  2. InfluxDB

    InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

    InfluxDB logo
  3. 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

  4. postgres-kafka-cassandra

    Data Pipeline between PostgreSQL and Cassandra using Kafka Connect

  5. nri-prometheus

    Fetch metrics in the Prometheus metrics inside or outside Kubernetes and send them to the New Relic Metrics platform.

  6. kafka-rest

    Confluent REST Proxy for Kafka

  7. SaaSHub

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

    SaaSHub logo
  8. firehose

    Firehose is an extensible, no-code, and cloud-native service to load real-time streaming data from Kafka to data stores, data lakes, and analytical storage systems. (by raystack)

  9. data-mesh-demo

    A Data Mesh proof-of-concept built on Confluent Cloud

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better kafka-connect-jdbc alternative or higher similarity.

kafka-connect-jdbc discussion

Log in or Post with

kafka-connect-jdbc reviews and mentions

Posts with mentions or reviews of kafka-connect-jdbc. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-08-31.
  • How Sendoso is using Kafka for Event-Driven Architecture
    3 projects | dev.to | 31 Aug 2021
    Event sourcing is an effective architectural pattern to record changes to the application state. Event sequence is important - we need changes as they were originally applied. incoming events are first persisted into Kafka and then processed by services independently. Kafka, hence, becomes our source of truth (SOT), a data source that gives a complete picture of the data object as a whole. This, however, meant dramatic changes in our core application. Our source of truth is still the core database, but we generate events in Kafka when data gets persisted. To ensure transactional behavior, we employed Transactional Outbox pattern. Essentially, we a) created a new events table in the database, b) wrote event data in the same transaction when we update our SOT table. Kafka Connect is subsequently used to read this table and insert records in relevant Kafka topics. This ensures that we never have an inconsistent situation where data was inserted in the database but the event is not added to Kafka topic or vice versa. We evaluated a few connectors for sourcing data from Mysql (JdbcSourceConnector, and Debezium). Our scenario was supported out of the box in JdbcSourceConnector, making it possible to have one event table in Mysql where different rows could be routed to a relevant topic based on the topic field.
  • Data Pipeline between PostgreSQL and Cassandra using Kafka Connect
    3 projects | dev.to | 18 Jan 2021
    This is different compared to the "polling" technique adopted by the Kafka Connect JDBC connector

Stats

Basic kafka-connect-jdbc repo stats
2
26
9.4
9 days ago

Sponsored
InfluxDB – Built for High-Performance Time Series Workloads
InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
www.influxdata.com

Did you know that Java is
the 8th most popular programming language
based on number of references?