Centralized
Centralized
Centralized
What is Centralized config?
What is Centralized config?
Consolidate configuration complexity into a single location.
Consolidate configuration complexity into a single location.
Why Centralized config?
Why Centralized config?
Easier to manage complexity within a single location versus multiple locations.
Avoid config sprawl. Making simple at the sprawl and managing it in the center.
Easier to manage complexity within a single location versus multiple locations.
Avoid config sprawl. Making simple at the sprawl and managing it in the center.
Benefits
Benefits
Syncing config to the edge (where it’s used) mitigates downtime.
Centralizing the configuration and generation of that configuration with transformations allows all the places that consume the configuration to be very simple.
Syncing config to the edge (where it’s used) mitigates downtime.
Centralizing the configuration and generation of that configuration with transformations allows all the places that consume the configuration to be very simple.
Examples
Examples
It's easier to fetch the configuration for service "X" versus coding all the logic needed to generate the configuration for service "X."
Complete a SecOps audit faster because secrets and change history are in one location versus sprawled across different systems and interfaces.
In a large system, the complexity of delivering configuration across all components becomes unmanageable. By centralizing, you reduce that complexity at the component level to just asking for targeted config and at the hub level by consolidating and reusing the configuration logic used to generate all the targeted configs. The node requests, “give me the json doc for serviceA for the production environment,” and the hub can leverage the common pattern to minimize the incremental cost of doing that for any similar request (new services, new environments, etc.)
It's easier to fetch the configuration for service "X" versus coding all the logic needed to generate the configuration for service "X."
Complete a SecOps audit faster because secrets and change history are in one location versus sprawled across different systems and interfaces.
In a large system, the complexity of delivering configuration across all components becomes unmanageable. By centralizing, you reduce that complexity at the component level to just asking for targeted config and at the hub level by consolidating and reusing the configuration logic used to generate all the targeted configs. The node requests, “give me the json doc for serviceA for the production environment,” and the hub can leverage the common pattern to minimize the incremental cost of doing that for any similar request (new services, new environments, etc.)