Authors :
Shreeson Shrestha Er.
Volume/Issue :
Volume 9 - 2024, Issue 11 - November
Google Scholar :
https://tinyurl.com/yyx98scj
Scribd :
https://tinyurl.com/54xxxx8f
DOI :
https://doi.org/10.38124/ijisrt/IJISRT24NOV1065
Note : A published paper may take 4-5 working days from the publication date to appear in PlumX Metrics, Semantic Scholar, and ResearchGate.
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
References :
- Pivotal Software, Inc. (n.d.). Spring Boot 3.3.x reference guide. Spring.io. Retrieved October 12, 2024, from https://docs.spring.io/spring-boot/docs/3.3.x/reference
- Spring Cloud. (n.d.). Spring Cloud Config: Centralized External Configuration Management. Spring.io. Retrieved October 15, 2024, from https://spring.io/projects/spring-cloud-config
- Docker, Inc. (n.d.). Docker Overview. Docker Documentation. Retrieved October 15, 2024, from https://docs.docker.com/get-started/overview/
- Spring.io. (n.d.). Spring Cloud Bus 4.1.x reference guide. Retrieved October 18, 2024, from https://docs.spring.io/spring-cloud-bus/docs/4.1.x/reference/html/
- Spring.io. (n.d.). Building a RESTful web service with Spring Boot Actuator. Retrieved October 18, 2024, from https://spring.io/guides/gs/actuator-service
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
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