Publication Date: 2024/12/04
Abstract: Spring boot microservices require the application runtime to pause until the services restart for the configuration refresh. Services linked to a centralized config server, or preferably, a config client, need this. Config client refresh played a critical role in maintaining the consistency and responsiveness of distributed microservices by dynamically updating client-side configurations without application downtime. This approach explored various strategies and optimizations for config client refresh to enhance system reliability. This Study investigated different available approaches of config client refresh mechanisms for impact on system behavior. This study experiment utilized the available spring packages, bash-scripts, and docker for the containerization of applications and collected performance metrics for analysis. Further, this approach identified key factors affecting refresh efficiency and proposed optimized techniques to mitigate potential challenges. Findings contribute a deeper understanding of configuration client refresh and offer pragmatic insights into designing robust and efficient scalable systems.
Keywords: Configuration Management, Config Refresh, Containerization, Distributed System, Microservice Architecture, Spring Cloud Config
DOI: https://doi.org/10.38124/ijisrt/IJISRT24NOV1065
PDF: https://ijirst.demo4.arinfotech.co/assets/upload/files/IJISRT24NOV1065.pdf
REFERENCES
6. Spring.io. (n.d.). Push notifications and Spring Cloud Bus in Spring Cloud Config. Retrieved October 19, 2024, from https://cloud.spring.io/spring-cloud-config/multi/multi__push_notifications_and_spring_cloud_bus.html