spring-projects / spring-projects/spring-modulith
Evaluate automatic purge mechanisms for completed events
Open
Nobody has claimed this yet.
in: event publication registry
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 222
- PR merge metrics
- No merged PRs in 30d
Description
- Archive table – instead of marking an event as completed in the "current table" we could write an archive table to contain older, completed events and the original one just get completed events wiped (two options in turn: archive on insert, archive on completion)
- Indexes (on event and publication target identifier)
- Sliding window (based on time, number of completed publications)
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
Compare the three approaches described in the issue: archive tables, indexes on event and publication target identifiers, and sliding-window retention. Start by mapping how completed events are currently stored and define which purge behavior, retention rule, and indexing strategy would satisfy the intended lifecycle. Done means a decided approach with its trade-offs and scope documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100