Hi All,

Since this is the first time I will be integrating my java backend service 
with etcd for configuration management.

I would like to know:

Design perspective:

1. For configurations that are bound to change on runtime, should we still 
keep them in memory (Map etc. ) so that when application modules needs 
those configurations on runtime, we don't query etcd everytime?

Implementation perspective:

1. What is the best strategy for features like 'watch'. What general 
actions would one perform when any configuration gets changed. Should we 
watch the directory recursively or single configuration etc. How to 
continuously watch for 'configuration'/'directory' change including the 
tasks like 'refreshing'/'clearing' of class member instances.?

Many thanks for your support.

Best Regards


Reply via email to