This article explains Apollo’s distributed configuration center, its overall architecture, the use of HTTP long polling with Spring’s DeferredResult, code examples for listening and publishing config changes, and strategies to ensure message reliability across multiple nodes.
The article examines why a distributed configuration system is needed, outlines its constraints, traces its evolution from single‑machine files to centralized and database‑backed stores, and presents WeChat’s design—key‑object protobuf model, secure SDK, asynchronous pull loading, versioned consistency, and gray‑release support—demonstrating a two‑year case study that cut configuration rollout time from days to minutes.
This article introduces the need for dynamic configuration in Spring Boot microservices, compares popular open‑source configuration centers such as Apollo, Nacos, Spring Cloud Config, Disconf, and Diamond, and provides detailed features, a comparison table, and code examples for integrating Apollo.
This article examines the architecture and features of Spring Cloud Config and Ctrip Apollo configuration centers, compares their strengths and weaknesses, and provides practical guidance for migrating from Spring Cloud Config to Apollo in microservice environments.
BRCC (Better Remote Config Center) is an open‑source, lightweight, Spring‑Boot‑based distributed configuration center that simplifies management of dynamic, multi‑environment settings across dozens of instances by offering easy SDK/API access, push notifications, traceability, fine‑grained security, high performance, and a user‑friendly UI.
This tutorial walks through creating a Spring Boot service, adding local configuration, moving the configuration to Nacos, integrating Nacos into the service, and enabling dynamic refresh so changes take effect without restarting the application.
The article introduces the need for a distributed configuration platform, outlines its typical scenarios and essential characteristics, and details the lightweight open‑source implementation Diablo—including its architecture, data model, Redis storage, client behavior, real‑time update mechanisms, and deployment recommendations.
