Eureka, ZooKeeper, and Nacos are common service registries in the Java microservices model. They handle service registration and discovery, and decouple services from each other to enable dynamic management. Enterprise Distributed Application Service (EDAS) supports these registries with different O&M methods.
Registry center
Service registries include Eureka, ZooKeeper, and Nacos. For more information, see the official website or GitHub repository for each registry to help you choose one based on your business needs.
EDAS provides hosting and microservices governance for your applications regardless of which service registry you use.
The available O&M methods depend on the service registry type.
Use Nacos
If you use Nacos as the service registry, two O&M options are available:
-
Use the shared service registry of EDAS
The shared service registry of EDAS integrates the commercial version of Nacos, providing service registration and discovery as a built-in, fully managed component.
Benefits
Benefits of the shared service registry:
-
Reduces the cost of deploying and maintaining a separate service registry.
-
Encrypts service registration and discovery calls to prevent unauthorized applications from discovering your services.
-
Integrates with other EDAS components to provide a complete microservices solution.
Operations
When you create or deploy a Kubernetes application, clear the Use the service registry configured for the application option. This overwrites the configured Nacos address so the application connects to the shared EDAS registry instead.
-
-
The application's registry configuration includes Operations for both MSE-hosted and self-managed Nacos.
When you create or deploy a Kubernetes application, select Use the service registry configured for the application. EDAS preserves the Nacos address configured in your application instead of replacing it with the shared EDAS registry address during deployment.
Note-
Make sure your service registry can communicate with the application that is hosted in EDAS over the network. For example, they must be in the same VPC.
-
Nacos 2.x does not support access from all regions. Therefore, the client cannot connect to port 9848.
-
To configure the Use the service registry configured for the application setting, see Configure microservices governance.
-Dnacos.use.endpoint.parsing.rule=false -Dnacos.use.cloud.namespace.parsing=false -
Use Eureka or ZooKeeper
If you use Eureka or ZooKeeper, you can choose an MSE-managed or a self-managed instance. For more information about MSE and the benefits of a managed service registry, see What is Microservices Engine (MSE)?.
Make sure your service registry can communicate with the application that is hosted in EDAS over the network. For example, they must be in the same VPC.
Operations
When you create or deploy a Kubernetes application in EDAS that uses Eureka or ZooKeeper, select Use the service registry configured for the application. For more information, see Configure microservices governance.
You can also replace Eureka or ZooKeeper with Nacos in the application configuration to use the shared service registry of EDAS.
Use other types of service registries
If you use another type of service registry, such as Consul, you must use a self-managed registry.
Make sure your service registry can communicate with the application that is hosted in EDAS over the network. For example, they must be in the same VPC.
Operations
If your application has a configured service registry, select Use the service registry configured for the application when you create or deploy the application in EDAS. For more information, see Configure microservices governance.
You can also replace the service registry with Nacos in the application configuration to use the shared service registry of EDAS.
FAQ
Why do I get an HTTP 403 error when connecting to the shared service registry of EDAS?
EDAS injects tenant authentication information, which has a lower priority than username-password authentication. Remove the username and password configuration for the service registry from the application to avoid this conflict.
How do I connect to an MSE service and configuration registry?
Associate a microservices namespace with an MSE Nacos instance when you create the namespace, then select this namespace when you create an application. For more information, see Create a microservices namespace.
When using the shared service registry, how do I read its configuration in my code?
The Application Configuration Management (ACM) feature integrated with EDAS is not affected by the discontinuation of the standalone ACM product. For information about how to write the code, see Dynamically push configurations using ACM.