Add 'Architecture' page
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 642
- Forks
- 70
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 21
Description
Create an architrcture diagram for Raphtory and matching explanation.
This diagram should include optional components like plugins and alternative UIs and should highlight the OSS vs closed storage solutions.
This is not intended to be an overview of the deployment architecture so we can be reasonably abstract and not talk about running X on Y machine. This should be done later.
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 mapping Raphtory's architecture, including optional plugins, alternative UIs, and OSS versus closed storage solutions. Done means a matching architecture diagram and explanation are provided, while deliberately excluding deployment details such as which component runs on which machine.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100