Thanks for the answers

I'll be looking for both to see what fits best for our needs :)

On Thu, Feb 12, 2015 at 12:37 PM, Colin <co...@clark.ws> wrote:
> Digital River will be releasing one soon as well that is integrated with the 
> netflix stack for discovery, load balancing, metrics,etc.
>
> --
> Colin Clark
> +1 612 859 6129
> Skype colin.p.clark
>
>> On Feb 11, 2015, at 7:20 PM, Jay Kreps <jay.kr...@gmail.com> wrote:
>>
>> Hey Justin,
>>
>> I don't think LinkedIn is, but Confluent has made a pretty complete
>> producer and consumer REST proxy that we will be releasing quite soon.
>>
>> -Jay
>>
>> On Wed, Feb 11, 2015 at 2:40 PM, Justin Maltat <justin.mal...@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> Is Linkedin planning to release its REST proxy server as an official
>>> release?
>>>
>>> This would be quite interesting for using Kafka in some existing
>>> heterogeneous  environment.
>>>
>>> Justin
>>>
>>>> On Thu, Jan 29, 2015 at 3:58 PM, Guozhang Wang <wangg...@gmail.com> wrote:
>>>> Thanks for sharing this Otis, I am also quite surprised about Python / Go
>>>> popularity.
>>>>
>>>> At LinkedIn we use a REST proxy server for our non-java clients, but
>>>> introducing a second hop will also bring more overhead as well as
>>>> complexities, such as producer acking and offset committing, etc. So I
>>>> think by the end of the day non-java clients will still be around.
>>>>
>>>> Guozhang
>>>>
>>>> On Wed, Jan 28, 2015 at 8:54 AM, Otis Gospodnetic <
>>>> otis.gospodne...@gmail.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I promised to share the results of this poll, and here they are:
>>> http://blog.sematext.com/2015/01/28/kafka-poll-results-producer-consumer/
>>>>>
>>>>> List of "surprises" is there.  I wonder if anyone else is surprised by
>>> any
>>>>> aspect of the breakdown, or is the breakdown just as you expected?
>>>>>
>>>>> Otis
>>>>> --
>>>>> Monitoring * Alerting * Anomaly Detection * Centralized Log Management
>>>>> Solr & Elasticsearch Support * http://sematext.com/
>>>>
>>>>
>>>>
>>>> --
>>>> -- Guozhang
>>>

Reply via email to