TechPrufer
Get started
Microsoft
Microsoft logoMicrosoft · Feature trail

Feature Flagging Patterns

3 posts · Mar 2016 – May 2022

What this trail covers

This thread tracks the evolution of feature flagging patterns and their integration into development workflows. It covers using feature flags for risk mitigation (kill switches), beta feedback and feature targeting (canary/dark launches), hypothesis-driven development (tying metrics to code), and long-term access control (subscription plans, SKU management). The integration with Visual Studio Team Services (VSTS) via extensions is also a key aspect, enabling flags to be tied per environment into Azure App Configuration. This post details the use of Azure App Configuration and GitHub Actions for deploying a Java Spring Boot application to Azure App Service, demonstrating how feature flags can control application behavior like enabling/disabling UI elements or features, and their application in A/B testing and blue-green deployments.

All Microsoft trails
  1. Deploy a Java application to Azure App Service using GitHub ActionsThis post introduces the use of Azure App Configuration and GitHub Actions for deploying a Java Spring Boot application to Azure App Service. It demonstrates how feature flags, managed via Azure App Configuration, can dynamically control application behavior, such as enabling or disabling UI elements (e.g., a mascot character). The post highlights the application of feature flags for A/B testing and blue-green deployments, explaining how percentages and time windows can be used to control feature rollout. It also mentions the ability to link external services via connection strings.
  2. Effective Patterns for Feature FlagsThis post introduces various patterns for using feature flags: kill switches for risk mitigation, beta feedback and feature targeting for granular user control (canary/dark launches), hypothesis-driven development for tying metrics to code and enabling iterative feature rollout, and subscription plans/SKU management for tiered access control. It highlights the integration of LaunchDarkly's feature flags with Visual Studio Team Services (VSTS) through a marketplace extension, allowing flags to be tied per environment into releases.
  3. New Build 2016 Partner Extensions in the Visual Studio Team Services MarketplaceThis post announces two new partner extensions for Visual Studio Team Services (VSTS) that were featured at Build 2016: LaunchDarkly and Redgate ReadyRoll. The LaunchDarkly extension integrates feature flagging capabilities into VSTS, allowing developers to tie feature flag rollouts to work items and manage them within the release pipeline. The Redgate ReadyRoll extension provides database schema change management for VSTS, supporting a migration-based approach and integrating with build and release management systems.