Distributed Configuration Center
In a distributed system, due to the huge number of multi-service, service profile in order to facilitate unified management, real-time updates, so they need the central component of a distributed configuration.
#Nacos Config
Nacos provided for storing configuration data and other metadata key / value store, the server and the client provides support for the external configuration of the distributed system. Use Spring Cloud Alibaba Nacos Config, you can centrally manage external attribute to configure your Spring Cloud applications in Nacos Server.
Spring Cloud Alibaba Nacos Config is an alternative to Spring Cloud Config Server and Client, the concept on the client and server with Spring Environment and PropertySource have a consistent abstract, in particular the bootstrap phase, the configuration is loaded into a Spring environment. When an application from development to test to production through the deployment pipeline, you can manage the configuration between these environments, and ensure that all content needs to run an application has migrated.
# Create a profile
Nacos Server needs to be created in the configuration file, we are still using YAML way to deploy configuration files procedure is as follows:
- Browser to open HTTP: // localhost: 8848 / nacos , access Nacos Server
- Create a new profile, here we created earlier service provider project as an example
Note: The default Data ID of the extension .properties, want to use YAML configuration, must be specified here is .yaml
- In a column published after the success of "Configuration List" to see just created configuration items
