Shekar, you mentioned:
> The API should give different status at each part of the pipeline. > At the ingestion, the API responds with "submitted" > During the progression, the API returns "in progress" > After successful completion, the API returns "Success" May I ask what your motivation is to know the status of each part of the pipeline? Do you need this information to, say, detect/prevent message loss? -Michael On Wed, Jun 29, 2016 at 8:39 AM, Shekar Tippur <ctip...@gmail.com> wrote: > I am looking at building a reactive api on top of Kafka. > This API produces event to Kafka topic. I want to add a unique session id > into the payload. > The data gets transformed as it goes through different stages of a > pipeline. I want to specify a final topic where I want the api to know that > the processing was successful. > The API should give different status at each part of the pipeline. > At the ingestion, the API responds with "submitted" > During the progression, the API returns "in progress" > After successful completion, the API returns "Success" > > Couple of questions: > 1. Is this feasible? > 2. I was looking at project reactor (https://projectreactor.io) where the > docs talk about event bus. I wanted to see if I can implement a consumer > that points to the "end" topic and throws an event into the event bus. > Since I would know the session ID, I can process the request accordingly. > > Appreciate your inputs. > > - Shekar >
