The purpose of Dyno
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 79
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
I was talking with @rclark about the purpose of Dyno vs the javascript object friendly AWS client last night and wanted to document what we said to help us keep focused on the new goals of this project since a large part of the original goal has been solved by AWS themselves.
1. Support reading from one region and writing to another
2. Better support for streaming
3. Better support for bulk read and write actions
I'd like to rework the README to clarify these goals. Is there anything else we should cover?
I'd also like to take a look at stuff dyno does that doesn't fall under the stated goals and talk about removing the functionality or being explicit that this is a goal. One thing Dyno does now that isn't mentioned above is provide cli support.
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 README against the three stated goals: cross-region reads and writes, streaming, and bulk actions. Clarify whether CLI support remains in scope and document the final project goals; resolve the open question about functionality outside those goals before editing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100