Apache Kafka is publish-subscribe messaging rethought as a distributed commit log.
0
votes
0answers
29 views
Distributed transactions with Kafka
I need to implement a transaction that spans over loosely coupled (SOA+MOM) components.
When a particular event is received, FOO and BAR need to do a transactional operation: that is, both the ...
0
votes
0answers
23 views
Working with an event firehose
When working with an event firehose to Kafka, what are some good strategies for tagging/formatting events in publishers, so they can be meaningful to the opaque consumers?
For example, I may have a ...
0
votes
2answers
137 views
Send heavy computation jobs from web server to another process and wait for response
I know it is a common practice to send cpu-bounded heavy tasks to background processes, in order to free a web server to serve other requests.
But - what if the request must know the result of that ...
0
votes
1answer
292 views
Backing up messages in S3 within a Storm topology
In my project we are trying to build up a KIND-of-a-lambda storm based architecture. The component would be responsible for indexing the site usage events so we expect a quite massive random load. The ...
1
vote
2answers
1k views
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?
From the Kafka documentation page it says:
each message in the partition are assigned a unique ...
