Clarification: 2.3.3 "entirety or it is rolled back "
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3.6k
- Forks
- 831
- Avg merge
- 7h 55m
- Merged PRs (30d)
- 4
Description
Verify that transactions are being used at the business logic level such that
either a business logic operation succeeds in its entirety or it is rolled back to
the previous correct state.
I have no concern on security goal, but the wording is biased toward monolithic ACID. How this requirement is verifiable for event-driven systems where Sagas or eventual consistency is used?
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
Review the ASVS 5.0 source and the raw .md master text for requirement 2.3.3, starting with the transaction wording quoted in the issue. Compare its verification goal with Saga and eventual-consistency approaches; done means reaching an agreed clarification or scope for event-driven systems and documenting the resulting wording.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100