Microservices Registry is a tool that is used to manage microservices. Microservices Registry helps developers register and discover services in a distributed system and enable services to communicate with each other. Microservices Registry provides the configuration management feature to support dynamic configuration updates. This simplifies the distribution and management processes of configurations.
Scenarios
Service discovery of microservice applications: In the microservices architecture, application instances may dynamically increase or decrease. Microservices Registry can help service consumers dynamically identify service providers.
Configuration management of distributed applications: Microservices Registry centrally manages application configurations and updates the configurations in real time. This way, manual modifications of configuration files are not required, configuration management efficiency is improved, and configuration consistency is ensured. Microservices Registry allows you to dynamically modify application configurations without the need to restart applications.
Centralized coordination of distributed applications: Microservices Engine (MSE) ZooKeeper instances provide a wide range of features such as distributed locks and distributed queues. Microservices Registry can provide distributed coordination components for big data systems such as Hadoop, HBase, Kafka, and Flink to improve high availability and quickly and efficiently build distributed application systems.
Benefits
Microservices Registry serves as an easy-to-use and high-performance platform. Microservices Registry provides various features for dynamic service discovery, configuration management, and service management. Microservices Registry provides the following benefits:
Ease of use: MSE provides fully managed services and supports mainstream instances such as Nacos, ZooKeeper, and Eureka instances. Manual deployment and maintenance are not required. Microservices Registry simplifies the registration, discovery, and configuration management of microservice applications.
High availability: Microservices Registry uses a high-availability architecture and supports cross-zone deployment. When an instance fails, failover occurs in seconds and the failed node is automatically removed from the available node list. This improves the risk resistance capability of applications.
High security: Microservices Registry supports fine-grained authentication of Nacos instances and Simple Authentication and Security Layer (SASL) of ZooKeeper instances. Microservices Registry integrates with Alibaba Cloud Key Management Service (KMS) to encrypt configurations for service and data security purposes.
High performance: Compared with open source instances, the performance of Microservices Registry instances is improved by more than 40%. This allows Microservices Registry to meet requirements for high concurrency and high loads.
Smooth migration: Microservices Registry is compatible with open source middleware such as Nacos, ZooKeeper, and Eureka, and supports smooth migration to reduce migration costs and risks.
Observability across the entire workflow: Microservices Registry supports more than 70 business and resource metrics. Microservices Registry allows you to query pushing tracks of services and configurations. This helps you monitor and manage services in real time.
Microservices Registry can improve the flexibility and scalability of the microservices architecture, reduce the complexity of service management, and improve the stability and performance of the system.
Features
Feature | Description | References |
Service management | Allows you to query and manage services on a Nacos or Eureka instance in a visual manner. This feature facilitates the management of services that are registered with instances. | |
Data management | Allows you to query and update data on a ZooKeeper instance in a visual manner. This feature helps you focus on business data. | |
Observation analysis | Displays engine metrics, such as the number of connections, transactions per second (TPS), and queries per second (QPS). This feature helps you identify system bottlenecks. | |
Alert management | Allows you to receive alert notifications by using text messages, emails, or DingTalk messages. This way, you can keep track of business exceptions in real time. | |
Cloud migration | Provides the cloud migration capability. When you use this feature, you can use MSE Sync, a GUI-based migration tool, to synchronize information between the source and destination instances. This way, the client can obtain information from both the source and destination instances. | Migrate self-managed instances to MSE Microservices Registry |
Configuration management | Allows you to create, synchronize, view, modify, and delete configurations. |
Get started with Microservices Registry
Service registration: If you want to use an MSE Nacos instance as a service registry for Spring Cloud applications, you can follow the instructions in Register Spring Cloud applications with MSE Nacos registries.
Configuration management: If you want to integrate an MSE Nacos instance as a configuration center in Spring Cloud applications, you can follow the instructions in Integrate an MSE Nacos configuration center with Spring Cloud applications.
References
For more information about the regions that are supported by Microservices Registry, see Supported regions.
For more information about the edition selection, upgrade, and billing of Microservices Registry, see Microservices Registry.