openedx / openedx/edx-rest-api-client
Ideas for improving resiliency of the client
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 23
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
It seems like it would be useful for the client to have additional resiliency capabilities such as retries, exponential backoff, auto-handling of rate limiting, circuit breaker, etc. that would both protect the caller and callee, both of which would be useful to prevent common situations where services fall like dominoes (e.g. Discovery, then LMS).
Each idea could be ticketed separately.
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
No files, tests, or entry points are named. Begin by selecting one capability from retries, exponential backoff, rate-limit handling, or circuit breaking and define its expected behavior and scope as a separate ticket. Then locate the client entry point and relevant tests before assessing implementation work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100