Consider using auto configured Kafka components from Spring Boot

Open
#2,910 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
java, kafka, spring-boot
Domain
backend, stream-processing

Research direction

Start by examining the Kafka binder’s producer and consumer factories, template, and listener infrastructure, then compare them with the components configured by Spring Boot and the Pulsar binder. Review the related context in issue 2909. Done means establishing whether the substitution is feasible and defining the required changes and implications.

Written by the indexing model from the issue text.

Description

enhancement

Currently, the Kafka binder provides its own producer and consumer factories, template, and listener infrastructure. Consider using the ones configured by the Boot as the Pulsar binder does. It is not a trivial task as some unknown/moving factors may exist. But look into the possibility. See this issue for somewhat related context: https://github.com/spring-cloud/spring-cloud-stream/issues/2909.

Dominant language
Java
Stars
1.1k
Forks
646
Avg merge
2d 3h
Merged PRs (30d)
8

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from spring-cloud/spring-cloud-stream

All issues in spring-cloud/spring-cloud-stream

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.