Dyno.session()
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 79
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
Spitballing an idea here, looking for feedback. What if Dyno.session() provided you a dyno client that could keep track of things across all the queries that you made within that session?
Some examples of what might be nice to have stashed in memory alongside your client:
- table definitions: knowing the key schema can allow you to calculate the size of items as they are stored in DynamoDB. It could also help with higher-level functions like https://github.com/mapbox/dyno/issues/101
- you could keep track of how much storage you've added within the session
- a running count on capacity consumed across requests within your session
cc @mick @emilymcafee @willwhite
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 by reviewing the existing Dyno client and the proposed Dyno.session() entry point, then read lib/item.js around the linked item-size calculation. Review issue #101 and determine which session state is in scope, including table definitions, storage added, and capacity consumed. Done should include an agreed design and implementation scope for tracking that state across queries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100