nspcc-dev / nspcc-dev/neofs-node
innerring: Cache Sidechain responses?
Open
Nobody has claimed this yet.
enhancement
I4
neofs-ir
performance
S3
U3
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
In current implementation innerring.Server doesn't cache Sidechain responses.
Pros
Inner Ring works with the Sidechain more synchronously.
Cons
More network load.
Possible solution
- continue working without cache
- cache all Sidechain responses for some time
2+. do (2) and subscribe for notifications which can invalidate/update cache
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 innerring.Server and trace how it obtains Sidechain responses. Compare the three caching approaches listed in the issue, including notification-based invalidation, and establish the intended consistency and lifetime behavior. Done means one approach is agreed upon and its cache behavior is implemented and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100