ddd-by-examples / ddd-by-examples/library
Patron Aggregate Concurrency Control
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5.9k
- Forks
- 831
- PR merge metrics
- No merged PRs in 30d
Description
I don't see any concurrency control for patron aggregate regardless of being the most important entity to hold the rules. Is it left intentional?
I changed a few code to test it out, and indeed there is no concurrency control. I can just hold two books which is violating the regularPatronMaximumNumberOfHoldsPolicy.
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
No file or test is named in the issue. Start by reproducing two concurrent hold requests and trace where the patron aggregate enforces regularPatronMaximumNumberOfHoldsPolicy; done means concurrent operations cannot exceed the policy, with a regression test covering the race.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100