Article on scaling changefeeds
Open
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 118
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
We should add an article detailing patterns and solutions for scaling changefeeds in productions.
One example: using rethinkdb proxy nodes to increase the number of open changefeeds, without actually storing data, allowing you to use proxy nodes as coordinators for large numbers of changefeeds.
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 documentation structure and any current changefeed material, then verify the rethinkdb proxy behavior described in the issue. The article is done when it explains practical patterns for scaling changefeeds, including how proxy nodes can coordinate many feeds without storing data.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100