-
-
Notifications
You must be signed in to change notification settings - Fork 658
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create feature-flag-best-practices.md #4804
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ivarconr
reviewed
Sep 21, 2023
ivarconr
reviewed
Sep 21, 2023
website/docs/topics/feature-flags/feature-flag-best-practices.md
Outdated
Show resolved
Hide resolved
ivarconr
reviewed
Sep 21, 2023
|
||
![feature-flag-scalable-architecture](https://github.com/Unleash/unleash/assets/87366358/e0ac76e0-992c-49ef-80be-70d2971ed937) | ||
|
||
**5. Real-Time Update Service**: Implement real-time updates in your application so that changes to feature flag configurations are immediately reflected without requiring application restarts or redeployments. The SDK should handle subscriptions or polling to the feature flag service for updates. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested change
**5. Real-Time Update Service**: Implement real-time updates in your application so that changes to feature flag configurations are immediately reflected without requiring application restarts or redeployments. The SDK should handle subscriptions or polling to the feature flag service for updates. | |
**5. Continuously Updated**: Implement update mechanisms in your application so that changes to feature flag configurations are reflected without requiring application restarts or redeployments. The SDK should handle subscriptions or polling to the feature flag service for updates. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated.
ivarconr
reviewed
Sep 21, 2023
ivarconr
reviewed
Sep 21, 2023
website/docs/topics/feature-flags/evaluate-flags-close-to-user.md
Outdated
Show resolved
Hide resolved
ivarconr
reviewed
Sep 21, 2023
ivarconr
reviewed
Sep 21, 2023
Co-authored-by: Ivar Conradi Østhus <ivar@getunleash.io>
Co-authored-by: Ivar Conradi Østhus <ivar@getunleash.io>
Co-authored-by: Ivar Conradi Østhus <ivar@getunleash.io>
Co-authored-by: Ivar Conradi Østhus <ivar@getunleash.io>
Co-authored-by: Ivar Conradi Østhus <ivar@getunleash.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
About the changes
Closes #
Important files
Discussion points