-
Notifications
You must be signed in to change notification settings - Fork 56
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
Native Ruby KCL #27
Comments
Hey @henadzit, I'm not related with AWS in any way, but I have implemented several KCL apps with this repository. I don't think they will develop a pure Ruby version as this is not updated since almost a year ago. Java is not running your Ruby code, it simply calls your ruby app using shell My recommendation is that you should not integrate this kind of apps with Rails in any way, however you can connect to your Rails app database using the PG gem or Sequel. |
@EdgarOrtegaRamirez, thank you for your reply.
I get it but it doesn't change much. We still need to build heavy Docker instances and write lots of code. To be honest, that's quite a bummer, especially, since Kinesis isn't cheap at all. We're considering moving to Apache Kafka because it seems to have better client libraries. |
Could you please describe heavy? Apache Kafka on the other side is pretty great 👍, you should use it |
@EdgarOrtegaRamirez I'm assuming this is what @henadzit is referring to: $ docker images
TAG SIZE
before-kcl 519MB
after-kcl 947MB Sitting at 428MB, It seems like Amazon has a C++ implementation of the Kinesis client. I'm thinking that the C++ implementation could be used as a native extension to this gems, which would remove the requirement to run a JVM. |
Hi, I made kcl-rb that is a client library written by pure ruby. |
Hello,
Are there plans on developing native Ruby Kinesis Client Library? Having the Java library running Ruby code when you have a simple Rails application is very far from optimal. It makes Docker instances heavy and requires lots of supporting code.
Thanks,
Henadzi
The text was updated successfully, but these errors were encountered: