Switch database connection between reading and writing rollup
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 354
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
First off: Thank you all for the work on Rollup (and all your other brilliant gems), much appreciated. I've been eyeing Rollup forever for our platform's metrics and can't believe I waited this long to implementing it.
As suggested by @dudadornelles here https://github.com/ankane/rollup/issues/8, it would be super useful to be able to perform the reads from a replica and only perform the upsert on the primary database. I didn't see an issue for it yet, so consider this my +1 for the idea.
Thanks again!
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. Start by tracing Rollup's existing database read and upsert flow, then determine how reads could use a replica while the upsert uses the primary. Done should mean the requested connection split is implemented without changing the intended rollup behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100