Will a MQ topic persist messages when one of the consumers is down [closed]
Closed 9 years ago.
Will a MQ topic persist messages when one of the consumers is down [closed]
Closed 9 years ago.
Will a MQ topic persist messages when one of the consumers is down [closed]
Closed 9 years ago.
Kafka, is it possible to get the message offset after producing?
While using Apache Kafka, is it possible to get the offset of the message that has been produced?
Kafka, is it possible to get the message offset after producing?
While using Apache Kafka, is it possible to get the offset of the message that has been produced?
Kafka, is it possible to get the message offset after producing?
While using Apache Kafka, is it possible to get the offset of the message that has been produced?
Kafka, is it possible to get the message offset after producing?
While using Apache Kafka, is it possible to get the offset of the message that has been produced?
Background thread processing vs queue based processing for relatively short tasks (max 30-40 seconds)
I need suggestion / recommendation on the design approaches mentioned below.
Handling rate limits / delays in consumers without affecting performance of other operations
I have a producer that generates a batch job that consists of multiple operations (approx. 100 – 10000). These operations can be processed in any order, ideally as fast as possible.
What can I do to get a message processor to slow down the rate of writes that it is making to a database?
We have this architecture: