You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Yes, currently our deployment process is tightly coupled with feature releases. Every time we need to launch a new feature or make a significant change, it requires a full deployment cycle. This not only slows down our ability to roll out features but also increases the risk of introducing bugs to our production environment. I'm always frustrated when we have to coordinate multiple team schedules for a release or rollback features in case of issues.
Describe the solution you'd like
I would like to implement a feature flags system within our application. This system should allow us to toggle features on and off without needing to redeploy the application. Specifically, it should enable:
Admin users to manage feature flags through a UI (create, read, update, delete).
Developers to check the status of feature flags in the code, enabling or disabling features based on these flags.
The system to be integrated with our existing Next.js app and PostgreSQL database, ensuring that changes to feature flags are reflected in real-time or near real-time in the application.
Is there any context that might help us understand?
Several tools and libraries in the market offer feature flagging capabilities, such as LaunchDarkly, Split.io, and Unleash. Each provides a way to manage feature toggles across environments, targeting specific users, and analyzing the impact of feature releases. However, integrating a third-party solution requires external dependencies and might not offer the level of customization we need. A custom solution would give us full control over the feature flag lifecycle and integration points within our application.
Would you be willing to help by making a PR?
Yes.
Additional context
I believe implementing a feature flags system will significantly improve our deployment process, reduce risks associated with releasing new features, and enhance our ability to perform A/B testing. This feature aligns with our goals of improving the reliability and agility of our product development lifecycle. I've attached a preliminary database schema and a rough architectural diagram of how the feature flags system could integrate with our current setup.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Yes, currently our deployment process is tightly coupled with feature releases. Every time we need to launch a new feature or make a significant change, it requires a full deployment cycle. This not only slows down our ability to roll out features but also increases the risk of introducing bugs to our production environment. I'm always frustrated when we have to coordinate multiple team schedules for a release or rollback features in case of issues.
Describe the solution you'd like
I would like to implement a feature flags system within our application. This system should allow us to toggle features on and off without needing to redeploy the application. Specifically, it should enable:
Admin users to manage feature flags through a UI (create, read, update, delete).
Developers to check the status of feature flags in the code, enabling or disabling features based on these flags.
The system to be integrated with our existing Next.js app and PostgreSQL database, ensuring that changes to feature flags are reflected in real-time or near real-time in the application.
Is there any context that might help us understand?
Several tools and libraries in the market offer feature flagging capabilities, such as LaunchDarkly, Split.io, and Unleash. Each provides a way to manage feature toggles across environments, targeting specific users, and analyzing the impact of feature releases. However, integrating a third-party solution requires external dependencies and might not offer the level of customization we need. A custom solution would give us full control over the feature flag lifecycle and integration points within our application.
Would you be willing to help by making a PR?
Yes.
Additional context
I believe implementing a feature flags system will significantly improve our deployment process, reduce risks associated with releasing new features, and enhance our ability to perform A/B testing. This feature aligns with our goals of improving the reliability and agility of our product development lifecycle. I've attached a preliminary database schema and a rough architectural diagram of how the feature flags system could integrate with our current setup.
The text was updated successfully, but these errors were encountered: