open-feature / open-feature/flagd
[CHORE] Identify and fix single points of failure in flagd architecture
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 997
- Forks
- 136
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 11
Description
The only single point of failure allowed should be unavailability of flagd Sync service during initialization.
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 the flagd architecture and tracing its failure paths, since the issue names no files or tests. Identify each single point of failure and determine whether it can be removed; done means that only unavailability of the flagd Sync service during initialization remains allowed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100