Course contentsShow
← Software Engineering
Lesson 732 of 1,93323. Configuration ManagementFree lesson

Configuration Changes Without Redeployment

Understanding when configuration should require redeployment versus allowing runtime changes, and the trade-offs of each approach.

Configuration Changes Without Redeployment

What you'll learn: You'll understand when configuration should require redeployment versus allowing runtime changes, and the trade-offs involved.

The Core Question

After you've separated configuration from code, a critical decision emerges: should changing a configuration value require rebuilding and redeploying your application, or should the application detect and apply changes while running?

Two Approaches

Redeployment-Required Configuration means configuration is loaded once at startup. To change a database URL or feature flag, you must redeploy the application. This is simpler and more predictable—the application's behavior is fixed for its entire lifecycle.

Runtime Configuration Changes allow the application to reload configuration without restarting. Change a timeout value in your configuration store, and the running application picks it up within seconds or minutes.

The Trade-offs

Runtime changes offer tremendous agility: fix a misconfiguration instantly, adjust feature toggles without downtime, or tune performance parameters on the fly. This is especially valuable for feature flags, rate limits, or non-critical settings.

However, they introduce complexity: your code must safely handle configuration reloads mid-operation, validate new values before applying them, and potentially deal with inconsistent states during transitions.

Redeployment-required configuration is simpler and safer. The application validates all configuration at startup (as you learned earlier), and you know exactly what configuration version is running. But every change requires a deployment cycle, which may be slow or risky for critical systems.

When to Choose Which

Use runtime changes for: feature flags, operational parameters (timeouts, retries), non-critical settings that change frequently.

Require redeployment for: database connections, security credentials, service endpoints, or anything where mid-flight changes could cause data corruption or security issues.

Key Takeaway: Runtime configuration changes offer flexibility but add complexity; redeployment-required configuration is simpler and safer—choose based on how critical, frequent, and risky each configuration change is.