App Configuration Service
Definition
A managed service for storing and managing application settings, feature flags, and configuration values separately from your code.
Use Cases
- Amazon: Gradual rollout and rollback of a new checkout experience using feature flags — Teams use feature flags and staged configuration changes to enable a new flow for a small percentage of traffic, monitor key metrics, then expand the rollout. If metrics regress, they disable the flag to revert behavior without redeploying. (Reduced release risk and faster incident mitigation by decoupling feature exposure from code deployments.)
- Netflix: Runtime feature toggles and experimentation to control user-facing behavior — Netflix is known for using extensive configuration and feature-flag style controls to manage experiments and safely change behavior across services, allowing rapid adjustments without full redeploys. (Faster experimentation cycles and improved operational control during incidents by quickly disabling problematic changes.)
- Microsoft: Centralized application settings and feature flags across multiple environments — Teams commonly use Azure App Configuration to store environment-specific settings and feature flags, with applications loading configuration at startup and/or refreshing periodically to pick up changes. (More consistent configuration management across dev/test/prod and fewer emergency redeployments for simple setting changes.)
Provider Equivalents
- AWS: AWS AppConfig
- Azure: Azure App Configuration
- GCP: Firebase Remote Config
- OCI: OCI Vault
Frequently Asked Questions
- What's the difference between an App Configuration Service and a secrets manager?
- An App Configuration Service stores non-secret settings like feature flags, endpoints, timeouts, and UI/behavior toggles. A secrets manager stores sensitive values like passwords, API keys, and certificates with strong access controls and rotation features. In practice, you often use both: config for behavior and secrets manager for credentials.
- When should I use an App Configuration Service?
- Use it when you need to change application behavior without redeploying, such as turning features on/off, doing gradual rollouts, running A/B tests, or managing environment-specific settings (dev/test/prod). It’s especially useful for microservices and multi-environment deployments where keeping configuration consistent and auditable is hard.
- How much does an App Configuration Service cost?
- Pricing typically depends on the number of configuration reads, stored configuration items, and (for some providers) deployment/rollout features. Costs increase with high-frequency polling, many applications/environments, and large numbers of feature flags. To control cost, cache configuration in the app, use push/refresh mechanisms when available, and avoid overly frequent polling.
Category: developer-tools
Difficulty: intermediate
Related Terms