spring-projects / spring-projects/spring-integration
Create separate implementations for MessageStore and MessageGroupStore [INT-2673]
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 1.2k
- Avg merge
- 17h 48m
- Merged PRs (30d)
- 62
Description
Gunnar Hillert opened INT-2673 and commented
Ultimately we might be able to provide a simpler more focussed implementation for the various use-cases (Aggregator versus Claim Check)
This may also lead to a simpler table setup for supporting plain MessageStore implementations e.g. used by Claim Check. This should help improving Scalability of Claim Check
This issue is a sub-task of #6647
Contributor guide
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 parent issue #6647 and the linked INT-2673 discussion. The issue proposes separate implementations for MessageStore and MessageGroupStore and possibly a simpler table setup, but it does not name files, tests, or a concrete completion boundary; clarify the design and scope before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100