of "t"
but I think the producers at the endpoint will be 100MB/S at the highest and
consumers between 25~30MB/S ...
De : Svante Karlsson
Envoyé : samedi 10 mars 2018 20:16:10
À : users@kafka.apache.org
Objet : Re: Suggestion over architecture
Ye
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 "kafka rest
p
ing
> message to our infrastructure side, but the webapp is unaware if it allowed
> or not ...
>
>
>
> thank for your reply 😊
>
> Adrien
>
>
> De : Svante Karlsson
> Envoyé : samedi 10 mars 2018 19:13:04
> À : users@kafka.apac
wed or not ...
thank for your reply 😊
Adrien
De : Svante Karlsson
Envoyé : samedi 10 mars 2018 19:13:04
À : users@kafka.apache.org
Objet : Re: Suggestion over architecture
You do not want to expose the kafka instance to your different clients. put
some api endpoi
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 your clients, they will se
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"
Hello all,
in my company we plan to set up the following architecture for our client:
An internal kafka cluster in our company, and deploy a webapp (our software
solution) on premise for our clients.
We think to create one producer by "webapp" client in order to push in a global
topic (in o
