Feature flags allow teams to control features dynamically. Which of the following best describes their main benefit?
Think about how feature flags help with deployment flexibility.
Feature flags let you enable or disable features at runtime without redeploying, which helps in gradual rollouts and quick rollbacks.
In a microservices system using feature flags, which component should hold the flag configurations to ensure consistency?
Consider how to keep feature flag states consistent across services.
A centralized feature flag service ensures all microservices get consistent flag values and can update flags dynamically.
You need a feature flag system for thousands of microservices worldwide. Which design choice best supports low latency and scalability?
Think about reducing network calls and load on central systems.
Local caching with a distributed cache reduces latency and load, allowing fast access to flags and scalability.
Feature flags enable quick feature toggling but introduce complexity. What is a major tradeoff to consider?
Think about what happens if flags are not cleaned up or managed well.
Feature flags add complexity and require careful management to avoid stale flags causing bugs or confusion.
Each feature flag state is stored as a boolean (1 byte). Estimate the total storage in megabytes needed to store all flags for all services.
Calculate total flags and convert bytes to megabytes (1 MB = 1,048,576 bytes).
5000 services * 100 flags = 500,000 flags. Each flag is 1 byte, so 500,000 bytes ≈ 0.48 MB, rounded to about 0.5 MB.