Git link : https://github.com/djrabi007/spring-c...
Spring Cloud Configuration By Github.
Spring Cloud config and Configuration related changes will reflect without restart/redeploy our application....
Server and Client side configuration in Distributed system...
We get central place to manage our external properties file...Declare all the properties in Global manner... i.e in Github.com which is accessible everywhere
2. Drawback without Cloud configuration ... Why Cloud Configuration ?
Solution :-
• All the Client are not directly interact with the Provider (A)...
• (C1,C2,C3)---Config Server application(B)---Github---A
• If A change it's URL, Then only need to Update GitHub....not all C1,C2,C3...
• B acts like a Gateway...
Demo purpose ,We will create the following
o 1 insurance Provider application(A)
o 1 insurance Config Server application (B) ---1 Client application (C1)
o -- Github repository to Update
https://github.com/djrabi007/insuranc...
3. Creating "Insurance-provconfig-server-rabi"
• Create Application with Actuator and Config Server
• @EnableConfigServer --- Will allow to invoke /actuator/default
• Access application.properties file from github
3.Creating Client
• XXXClient(9090)----XXserver(8888)--Github(*.properties)---XXService(8080)
• @RefreshScope--Url change in XXService and Github will reflect. ****ConfigClient******
• @Value--Fetch *.properties through XXserver(8888)--Github(*.properties)