kafka-connect-jdbc
firehose
Our great sponsors
kafka-connect-jdbc | firehose | |
---|---|---|
2 | 3 | |
997 | 313 | |
1.2% | 1.0% | |
7.3 | 2.5 | |
7 days ago | 10 months ago | |
Java | Java | |
GNU General Public License v3.0 or later | Apache License 2.0 |
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-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
firehose
-
Modern open-source data platform that empowers organizations to discover, transform, analyse and secure data faster and efficiently.
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.
- Firehose: Ingest streaming data to various sinks like HTTP REST, GRPC, and various databases. Firehose on daily basis ingest billions of events to our data warehouses and other storage systems. It is Open Source. Check it out and shoot us a star.
- No-Code Kafka sink to stream Protobuf/JSON data
What are some alternatives?
nri-prometheus - Fetch metrics in the Prometheus metrics inside or outside Kubernetes and send them to the New Relic Metrics platform.
kafka-connect-cosmosdb - Kafka Connect connectors for Azure Cosmos DB
kafka-connect-elasticsearch - Kafka Connect Elasticsearch connector
mongo-kafka - MongoDB Kafka Connector
kafdrop - Kafka Web UI
kafka-streams-in-action - Source code for the Kafka Streams in Action Book
kafka-rest - Confluent REST Proxy for Kafka
transit - A bytes first implementation of the Kafka API within an S3 keyspace
cosmosdb-cassandra-kafka
Apache Kafka - Mirror of Apache Kafka
postgres-kafka-cassandra - Data Pipeline between PostgreSQL and Cassandra using Kafka Connect
siren - Siren provides an easy-to-use universal alert, notification, channels management framework for the entire observability infrastructure.