loopbackio / loopbackio/loopback4-example-kafka
Bad Consumer implementation in KafkaConsumer Controller
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 11
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
If you activate the 'consumer.on message' event, this never ends, you will hear the messages until eternity.
Although there is a consumer, the closure of something happens with the life cycle and the consumer's problems a little more after sending the response.
Maybe I should wait for the consumer.close callback to issue the answer.
Therefore, if the controller issues his response and after this, the listener adds a new message to the response, we will get this error.
By definition, the consumer of Kafka behaves like a service or a demon and must start as a process at the beginning of the application.
Could you explain the best practice to do this? In loopback 3 we would use 'boot' directory to add a file with this responsibility.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the KafkaConsumer Controller and the consumer.on message lifecycle described in the issue. Compare the requested startup responsibility with the LoopBack 3 boot directory approach. Done means documenting the recommended way to run the Kafka consumer as an application-started service and avoid sending responses after the controller lifecycle ends.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kafka, typescript
- Domain
- backend, distributed-systems
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100