open-feature / open-feature/protocol
OpenFeature Remote Evaluation Protocol
@thomaspoignant is already working on this.
Since Oct 17, 2024.
- Dominant language
- No language data
- Stars
- 56
- Forks
- 7
- Avg merge
- 1h 54m
- Merged PRs (30d)
- 1
Description
Description
The OpenFeature Remote Flag Evaluation Protocol is a mechanism that allows generic providers to connect to any feature flag service that supports the protocol.
Currently, feature flag vendors are expected to write OpenFeature providers for every language they support. With the wire protocol, they would only be required to implement a single set of endpoints (technology needs to be defined), that could be consumed directly by all of the OpenFeature SDKs.
If the wire protocol does not provide the required capabilities for the vendor, they could write language-specific providers if they wish.
Goals
- Define the remote flag evaluation protocol.
- Support both the client and server SDK paradigms.
- Define the behavior of a generic provider
- Implement OFREP in multiple languages
Non-goals
- In-process flag evaluation
- Standard feature flag form definition (DSL)
Design Principles
- Follow browser and networking standards.
- Optimize for low latency and overhead.
- Consider the impact on privacy and security.
Resources
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.
Assessment
This issue has not been assessed yet.