Torben Sorensen
1bd27d7112
1005 B
ADR-024: Feature Flagging Strategy
Date: 2025-12-12
Status: Proposed
Context
As the application grows, there is no way to roll out new features to a subset of users (e.g., for beta testing) or to quickly disable a problematic feature in production without a full redeployment.
Decision
We will implement a feature flagging system. This could start with a simple configuration-based approach (defined in ADR-007) and evolve to use a dedicated service like Flagsmith or LaunchDarkly. This ADR will define how feature flags are created, managed, and checked in both the backend and frontend code.
Consequences
Positive: Decouples feature releases from code deployments, reducing risk and allowing for more controlled, gradual rollouts and A/B testing. Enables easier experimentation and faster iteration. Negative: Adds complexity to the codebase with conditional logic around features. Requires careful management of feature flag states to avoid technical debt.