kafka-connect-file-pulse
kafka-connect-jdbc
Our great sponsors
kafka-connect-file-pulse | kafka-connect-jdbc | |
---|---|---|
4 | 2 | |
305 | 997 | |
2.3% | 1.2% | |
8.9 | 7.3 | |
15 days ago | 3 days ago | |
Java | Java | |
Apache License 2.0 | 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.
kafka-connect-file-pulse
- Kafka Connect Filepulse 2.13.0 is now available! This version includes support for SFTP and Alibaba OSS. It also contains many bug fixes and improvements. 🚀
-
Download json and csv file from github repository with apache kafka
E.g., https://github.com/streamthoughts/kafka-connect-file-pulse
-
Streaming data into Kafka S01/E04 — Loading Log files using Grok Expression
Note : You can also install the connector either from GitHub Releases Page or from Confluent Hub.
kafka-connect-jdbc
-
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
What are some alternatives?
mongo-kafka - MongoDB Kafka Connector
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.
kafka-connect-elasticsearch - Kafka Connect Elasticsearch connector
nri-prometheus - Fetch metrics in the Prometheus metrics inside or outside Kubernetes and send them to the New Relic Metrics platform.
kryptonite-for-kafka - Kryptonite for Kafka is a client-side 🔒 field level 🔓 cryptography library for Apache Kafka® offering a Kafka Connect SMT, ksqlDB UDFs, and a standalone HTTP API service. It's an ! UNOFFICIAL ! community project
kafka-connect-transform-xml - Transformation for converting XML data to Structured data.
kafdrop - Kafka Web UI
PretendYoureXyzzy - A web clone of the card game Cards Against Humanity.
kafka-rest - Confluent REST Proxy for Kafka
kafka-connect-client - Java client library for Apache Kafka Connect REST Interface
cosmosdb-cassandra-kafka