Open Fodoj opened 9 years ago
Hi,
The KPL does not require a "multilang daemon" architecture; the basic idea is that your application in whichever language should communicate with the KPL binary using unix pipes/named pipes. A thin wrapper in Ruby should be all that is required.
We do plan to add wrappers in other languages, but don't have dates at present.
@gharikum so best practice would be to deploy KPL as a system service on every events producing node and then pipe any required data to this local system service, is that correct?
Currently the native code only supports one channel, so using it as a system-wide service would not work. It is better to launch it as child processes to your application processes, the same way the Java wrapper does.
@Fodoj - Curious if you got this working for your Ruby app. In a similar situation. Thanks.
@findchris - Nope, I didn't have an actual use case so I did not continue my investigation
@gharikum - Any progress on a Ruby interface to the KPL?
Seems strange that multi-language support is a first class citizen in the KCL, but not so in the KPL (the KCL's counterpart).
@kevincdeng - Been a while since your last comment; any updates here?
We're currently investigating ways to make adding additional language support easier, and will prioritize this with other improvements.
Other please comment, and add reactions to assist us in prioritizing this.
Related for .NET support: https://github.com/awslabs/amazon-kinesis-producer/issues/9
Did anyone implement KPL as a child process for Rails App? Any helpful links, Please? Thanks.
Is there a plan to add MLD similar to KCL daemon? I need to write producer in Ruby and thinking between using API and KPL, but KPL would require jruby currently :\