You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! What are the plans for this library in the medium/long term? After racecar migrated from ruby-kafka to rdkafka-ruby, I saw a few comments about slowing down the development of this library in favour of rdkafka-ruby.
See:
We are trying to choose a library to write to Kafka, and saw those comments recommending rdkafka-ruby instead but it doesn't support IAM roles (A feature we need). So we are favouring ruby-kafka but we are a little bit concerned that the library could become unmaintained in the future.
The text was updated successfully, but these errors were encountered:
As one of the contributors, I can say this library is pretty much abandoned and should no longer be considered for any production usage lasting long. As @dasch said in the comment and on a few other occasions, there is no point in trying to keep up with Kafka development when other languages use a well-established C binding and it gets more official support.
On top of that, I do get reports of users of Karafka 1.4 (ruby-kafka version based) that highlight either design issues, stability issues, or bugs and I do not expect them to be fixed.
Overall: not recommended, I would consider it either in a maintenance mode or fully abandoned.
Hello! What are the plans for this library in the medium/long term? After
racecar
migrated fromruby-kafka
tordkafka-ruby
, I saw a few comments about slowing down the development of this library in favour ofrdkafka-ruby
.See:
We are trying to choose a library to write to Kafka, and saw those comments recommending
rdkafka-ruby
instead but it doesn't support IAM roles (A feature we need). So we are favouringruby-kafka
but we are a little bit concerned that the library could become unmaintained in the future.The text was updated successfully, but these errors were encountered: