Skip to content
This repository has been archived by the owner on Jun 4, 2021. It is now read-only.

Evaluate Confluent Kafka client #588

Closed
matzew opened this issue Sep 13, 2019 · 11 comments
Closed

Evaluate Confluent Kafka client #588

matzew opened this issue Sep 13, 2019 · 11 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@matzew
Copy link
Member

matzew commented Sep 13, 2019

Currently both, channel and source are using the Sarama library for producer/consumer parts.

Ideally we use a more improved, high-level, API like the kafka lib from Confluent (Apache2 licensed). but the CGo dependency might be an issue...

@matzew
Copy link
Member Author

matzew commented Sep 13, 2019

With the regard of DQL support, this lib is also "interesting":

https://github.com/uber-go/kafka-client

but I have no idea on the actual PERF

@lionelvillard
Copy link
Member

The DQL support seems compatible with our design, one DLQ per topic and allowing DLQs to be on different clusters.

This API is alpha though....

@matzew
Copy link
Member Author

matzew commented Sep 16, 2019

@lionelvillard right, that's exactly why I put the DQL comment in here :-)

@matzew
Copy link
Member Author

matzew commented Sep 16, 2019

related: #596

@slinkydeveloper
Copy link
Contributor

IMHO I think sarama works well as a library. I think we should however improve our usage of it. On example could be: move message dispatching outside the goroutines that handles the partition processing

@matzew
Copy link
Member Author

matzew commented Sep 17, 2019 via email

@haneefkassam
Copy link

The other problem with the Confluent library is the external dependency on librdkafka, the installation of which requires some dependencies. Sarama being pure go alleviates some of those concerns.

@matzew
Copy link
Member Author

matzew commented Sep 25, 2019 via email

@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 11, 2020
@pierDipi
Copy link
Member

We evaluated and decided to use sarama.
/close

@knative-prow-robot
Copy link
Contributor

@pierDipi: Closing this issue.

In response to this:

We evaluated and decided to use sarama.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

6 participants