-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add rdkafka support #13535
Comments
Do you have any updates? I can't wait for it |
Any update? |
Hi, do you have any update on this merge request ? We are currently facing this issue in my entreprise. |
Hey, I've seen that @confluentinc/kafka-javascript is now in "limited availability" instead of "early access". So it seems that now is more stable to be used and maybe now we can move forward with this migration. Do you need help with something? I'm not an expert but I can try to assist if it's within my capabilities |
Let's track this here #13538 |
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
KafkaJS is no longer being actively maintained see tulios/kafkajs#1603
Describe the solution you'd like
To use a library with
librdkafka
bindings instead of the pure javascript implementation provided bykafkajs
.See #12703 (comment)
To use the
@confluentinc/kafka-javascript
because Confluent Inc. now maintains the underlying librdkafka library. The@confluentinc/kafka-javascript
may not be "production ready" but the developers on the project are actively working on getting it production ready.Teachability, documentation, adoption, migration strategy
This new microservice transport option needs to be documented.
TODO: Expand upon this.
What is the motivation / use case for changing the behavior?
The motivation around this feature is to migrate towards a javascript kafka library that will be maintained in perpetuity.
The text was updated successfully, but these errors were encountered: