- kafka-connect-jdbc VS kafka-connect-file-pulse
- kafka-connect-jdbc VS kafka-connect-elasticsearch
- kafka-connect-jdbc VS postgres-kafka-cassandra
- kafka-connect-jdbc VS kafka-rest
- kafka-connect-jdbc VS nri-prometheus
- kafka-connect-jdbc VS firehose
- kafka-connect-jdbc VS cosmosdb-cassandra-kafka
- kafka-connect-jdbc VS data-mesh-demo
- kafka-connect-jdbc VS kafdrop
- kafka-connect-jdbc VS opensearch-connector-for-apache-kafka
Kafka-connect-jdbc Alternatives
Similar projects and alternatives to kafka-connect-jdbc
-
-
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.
-
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
-
-
-
nri-prometheus
Fetch metrics in the Prometheus metrics inside or outside Kubernetes and send them to the New Relic Metrics platform.
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
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)
-
-
kafka-connect-jdbc discussion
kafka-connect-jdbc reviews and mentions
-
How Sendoso is using Kafka for Event-Driven Architecture
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
This is different compared to the "polling" technique adopted by the Kafka Connect JDBC connector
Stats
confluentinc/kafka-connect-jdbc is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of kafka-connect-jdbc is Java.