You could do every producer consume on a specific partition of response topic
(no high level consume) and send that number on the message... when the
consumer process the data, it sends the answer to the specific partition
Enviado do meu iPhone
Several answers in this thread seem to indicate Kafka can not be used to
simulate RPC.
In Joe Stein's Real-Time Distributed and Reactive Systems presentation,
RPC style calls look like they can be part of a system built using Kafka.
Reference : https://youtu.be/wRzL-0VSpTY?t=5m19s
The video
Thank you for your response. I have gone through the protocol wiki. Now I
have some understanding of it.
Sorry for again asking the question.
I want to know, Is it possible:
Let say, I have producer PA,PB,PC. They send request messages A,B,C
respectively. Now these messages goes to topic. There
Wrong use-case. Kafka is a queue (in normal case a TTL (time to live) on
messages). There is no correlation between producers and consumers. There
is no concept of a consumed message. There is no request and no
response.
You can produce messages (in another topic) as result of your processing
but
Thank you so much Svante for your response.
The application which we are designing depends lot upon request/response
mechanism. In that case should we move to some other message broker? If
yes, Can you please tell me the name which is best for this use case and
can handle large amount of
Why do you want a message broker for RPC?
What is large amounts of requests?
/svante
2014-09-22 12:38 GMT+02:00 lavish goel lavis...@gmail.com:
Thank you so much Svante for your response.
The application which we are designing depends lot upon request/response
mechanism. In that case
Thank you Svante for response.
*Below are some requirements that makes us to consider Message Broker.*
1. We have to handle 30,000 TPS.
2. We need to prioritize the requests.
3. Request Data should not be lost.
Thanks
Regards
Lavish Goel
On Mon, Sep 22, 2014 at 4:20 PM, svante
1 ) HA proxy - node.js (rest api). Use aerospike as session store if you
need one.
2) Difficult since the prioritization must be passed to lower levels and
that's usually hard. (Get rid of this constraint and go for a SLA - like
99,9% within 50ms or something like that)
2b) Group you customers
Agree with Svante, for your use case Kafka can be used to retain your
request messages, but it is not proper for RPC usages.
On Mon, Sep 22, 2014 at 6:06 AM, svante karlsson s...@csi.se wrote:
1 ) HA proxy - node.js (rest api). Use aerospike as session store if you
need one.
2) Difficult
Hi,
Please tell me how to use request/response mechanism in kafka?
Thanks
Lavish Goel
Do you mean that you want to know the protocol?
https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol
Guozhang
On Fri, Sep 19, 2014 at 12:18 PM, lavish goel lavis...@gmail.com wrote:
Hi,
Please tell me how to use request/response mechanism in kafka?
Thanks
Lavish
Thank you for your response. I want to implement request/response type
model.
For eg. I have a producer that publish a message(He wants to know some
status) to topic. A consumer pulls the message and processes the request.
Now I want that, the response of this request should go that producer. Can
12 matches
Mail list logo