Apollo Configuration Center: Overview, Features, Architecture, and Usage
This article provides a comprehensive overview of Apollo, an open‑source configuration management center, detailing its background, core concepts, architecture, deployment, client integration, key features such as real‑time updates, versioning, gray releases, permission control, and operational considerations for high availability.
Apollo is an open‑source configuration management center developed by Ctrip, designed to centrally manage key‑value configurations across applications, environments, clusters and namespaces, with real‑time push, versioning, gray release, and fine‑grained permission control.
The platform supports four dimensions (application, environment, cluster, namespace) and provides native Java and .Net clients, Spring integration, HTTP APIs, and an open platform API for external usage.
Key features include unified management of multi‑environment/cluster configurations, hot‑update of changes within seconds, versioned releases with rollback, gray releases, audit logs, and client‑side monitoring of configuration usage.
Deployment is simple, requiring only Java and MySQL, with provided packaging scripts; the architecture combines Config Service, Admin Service, Eureka, and Meta Server, often co‑located in a single JVM for high availability.
Clients maintain long‑polling connections for push notifications and periodic pull for fallback, cache configurations locally, and can listen for changes; the system integrates with Spring Cloud and uses Eureka for service discovery.
Operational considerations cover high availability scenarios, showing that individual service failures have no impact due to stateless design and load‑balancing across multiple instances.
Developers are encouraged to contribute via the GitHub repository (https://github.com/ctripcorp/apollo) and can submit pull requests.
Ctrip Technology
Official Ctrip Technology account, sharing and discussing growth.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.