Hi Kafka users and developers,
We are going to host our quarterly Stream Processing Meetup@LinkedIn on Mar
21. There will be three talks about Apache Pulsar, Apache Calcite and
Apache Samza, as well as LinkedIn's latest K-V store Venice built on top of
Apache Kafka and Apache Samza.
Please check
You right, but I'm afraid about the unauthorized queries' rate that the
endpoint can receive... which can become a bottleneck ...
But for now I think how I can estimate the partition's number. Due to the
formula max(t/p, t/c) I don't really know at the moment the real number of "t"
but I think
Don't worry :-) I understood. Thank a lot !
Adrien
De : Svante Karlsson
Envoyé : samedi 10 mars 2018 20:16:10
À : users@kafka.apache.org
Objet : Re: Suggestion over architecture
Yes, but I misread his reply and thought that he meant the
Yes, but I misread his reply and thought that he meant the "kafka rest
proxy". But now I see that we say the same thing - sorry for the confusion.
The normal way to do the authentication and authorization would be in the
rest/grpc endpoint before sending it to kafka.
2018-03-10 19:39 GMT+01:00
From: Svante Karlsson
Sent: Friday, March 2, 2018 3:50 PM
To: users@kafka.apache.org
Subject: Re: Consultant Help
try https://www.confluent.io/ - that's what they do
Thank Nick, thank Svante,
Svante, you say like Nick right ? Send a client message type which encapsulates
the emailing to a REST endpoint in our infrastructure and the endpoint
push into a kafka's topic ?
And if we need to ensure that client which send any emailing is allowed, where
you
Hi,
We are experimenting upgrading our kafka service from 0.10.2 to 1.0.1, and
noticed that it was slow in restarting the broker after updating the kafka
binary. On a test cluster that have ~120G data on each broker, it took
about 20 minutes to load log segments. I am wondering if there is any
You do not want to expose the kafka instance to your different clients. put
some api endpoint between. rest/grpc or whatever.
2018-03-10 19:01 GMT+01:00 Nick Vasilyev :
> Hard to say without more info, but why not just deploy something like a
> REST api and expose it to
Hard to say without more info, but why not just deploy something like a
REST api and expose it to your clients, they will send the data to the api
and it will in turn feed the Kafka topic.
You will minimize coupling and be able to scale / upgrade easier.
On Mar 10, 2018 2:47 AM, "adrien ruffie"