Functional Seams with Feature Flags

Hello there! In our previous lesson, we explored functional seams with functions as parameters, focusing on how they allow for safe code modifications and enhance testability. In this lesson, we'll explore another powerful tool: feature flags. Feature flags enable developers to toggle functionality in code, providing a flexible way to introduce new features without disrupting existing systems.

In software development, introducing new features often comes with the risk of disrupting existing functionality. Feature flags offer a solution by allowing developers to control the activation of features. This means we can deploy new code to production without immediately exposing it to users, reducing the risk of unforeseen issues. Feature flags also facilitate A/B testing, enabling us to gather user feedback on new features before a full rollout. By using feature flags, we can manage feature rollouts more effectively, ensuring a smoother development process.

Let's examine how to implement feature flags using a practical example, using our well-known OrderProcessor class. We can introduce an enum, OrderCalculationMode, to represent different calculation modes: Normal, Discount, and Surcharge. By passing this enum as a parameter to the ProcessOrder method, we can toggle between different behaviors.

public enum OrderCalculationMode
{
    Normal,       // Default calculation
    Discount,     // Apply 10% discount
    Surcharge     // Apply 15% surcharge
}

public class OrderProcessor
{
    public bool ProcessOrder(Order order, OrderCalculationMode calculationMode = OrderCalculationMode.Normal)
    {
        // ... order processing logic ...
        order.OrderTotal = CalculateTotal(totalAmount, calculationMode);
        return true;
    }

    private decimal CalculateTotal(decimal totalAmount, OrderCalculationMode calculationMode) => 
    calculationMode switch
    {
        OrderCalculationMode.Discount => totalAmount * 0.9m,  // 10% discount
        OrderCalculationMode.Surcharge => totalAmount * 1.15m,  // 15% surcharge
        _ => totalAmount // covers all other cases
    };
}

In this example, the ProcessOrder method uses the OrderCalculationMode enum to determine how to calculate the order total. By default, it uses the Normal mode, ensuring existing functionality remains unchanged unless explicitly specified otherwise. This approach allows for flexible feature management, enabling us to introduce new behaviors without altering the established codebase.