spring-projects / spring-projects/spring-modulith
Distribution of persisted event processing
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 222
- PR merge metrics
- No merged PRs in 30d
Description
As discussed on yesterdays JUG in Münster:
Modulith applications may be scaled horizontally to handle load. Decoupling of functional gravity via events may then cause a new bottleneck when scheduled reprocessing of failed handlers can only be executed by a single instance (e.g. using ShedLock).
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 with the Spring Modulith events reference linked in the issue and review the ShedLock example to understand the current single-instance scheduled reprocessing constraint. Clarify the intended distribution model for failed event-handler processing and define how horizontal scaling should be validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- 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