Microservices are all about decomposing your system into separate components. However, some things in a system seem like centralized in nature. My concern is about the system settings. In a monolith you have one big file / db with all the parameters, settings and preferences. This can be updated, backup, restore, export, import etc (think about Windows registry). More than this, your customers are used to go to this one "place" and set the system. With microservices architecture this "centralism" seems like an anti pattern.
What are the mechanisms/ frameworks to deal with such contradiction?
Central configuration server provides configurations (properties) to each micro service connected. As mentioned in the above diagram, Spring Cloud Config Server can be used as a central cloud config server by integrating to several environments.
Microservices – Centralized Configurations With Spring Cloud Config. Spring cloud config is provides externalized configurations for a distributed application. Here I'm going to explain how we can set up a spring cloud configuration server and consume that configuration server with a spring boot microservices project.
Have you already looked at projects like ZooKeeper, etcd or Consul? These can provide facilities to manage your configuration settings and service discovery.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With