spring-cloud / spring-cloud/spring-cloud-stream
Add support for aggregated destination
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 646
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 8
Description
There are times when a consumer destination may be represented by several physical destinations.
And while this is actually already supported by the framework, the actual mechanism creates multiple listener containers per each destination which may not be the most optimal solution.
Aggregate destination will allow one to identify which physical destination should be handled by a single listener container.
See more details in the discussion here
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 reading the discussion linked from issue 1168, especially the referenced comment in issue 1167, to understand the proposed aggregated-destination behavior. Define the expected configuration and lifecycle behavior there before identifying implementation and verification points; done means one listener container can handle the intended physical destinations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100