nuts-foundation / nuts-foundation/nuts-node
Optimise transaction processing with less DB writes
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
Transactions in a single message can be written with less DB transactions because the kid can be used to analyze which TXs are dependant.
See also transaction optimisation problem test.
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
Start with the transaction optimisation problem test mentioned in the issue, then trace the transaction-processing path it exercises. Determine how the kid identifies dependencies between transactions and verify that the change reduces database writes without changing processing results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100