Can you demo a bit more advanced scenario that when remote config changes, a bean variable gets updated automatically and reflected by whatever the bean is working on?
Nice, but how it stand to the fact that config server is running git pull on every call to health endpoint and it get up to date with remote repository in seconds. Can we integrate this wis bus event? Or maybe this is a bug not a feature and proper solution is to use monitor? But then what with cluster config server, that can be deployed on different data centers? We will need then a load balancer before it.
Very I nice. I have two questions 1] how dos this auto refresh of configurations works with enterprises hving strict and lengthy change management process? 2] why to add additional moving components like messaging, git. In highly transacted apps running in restricted resources, spring context restarts are too frequent which requires git to be highly available. I don't think this is a native approach to d the thing
do you have this example but using the bus kafka ??
Thank you , Josh!
Why did you add the reactive web dependency to config-server? It runs on tomcat anyway
Can you demo a bit more advanced scenario that when remote config changes, a bean variable gets updated automatically and reflected by whatever the bean is working on?
Nice, but how it stand to the fact that config server is running git pull on every call to health endpoint and it get up to date with remote repository in seconds. Can we integrate this wis bus event? Or maybe this is a bug not a feature and proper solution is to use monitor? But then what with cluster config server, that can be deployed on different data centers? We will need then a load balancer before it.
idol jlong... hitting bus refresh in config server doesn't refresh but works if I hit config clients
Awesome
Very I nice. I have two questions
1] how dos this auto refresh of configurations works with enterprises hving strict and lengthy change management process?
2] why to add additional moving components like messaging, git. In highly transacted apps running in restricted resources, spring context restarts are too frequent which requires git to be highly available. I don't think this is a native approach to d the thing
Please some helps me how to master in spring 😅😅
I've sent you a message
@@ChrisB_Crisps great
@@J-Ind24 just a bit
Too much hand action 😆