Enterprise Distributed Application Service:Select an O&M method for your service registry

Service registries

EDAS supports the following service registries: Eureka, ZooKeeper, and Nacos. For more information about each service registry, visit the corresponding official website or GitHub repository. You can choose a service registry based on your actual needs.

EDAS provides hosting and microservices governance services for your applications, regardless of the type of service registry that your applications use.

EDAS provides various O&M methods to cater to different types of service registries that your applications use.

Use Nacos

If you use Nacos as the service registry, the following two options are available:

• Use the shared service registry of EDAS

  EDAS integrates the general availability (GA) version of Nacos. EDAS provides the service registration and discovery capabilities of Nacos in the form of a shared service registry that does not require O&M.

  Benefits

  The shared service registry of EDAS provides the following benefits:

  • The shared service registry saves the costs for the deployment and O&M of a service registry.

  • Links are encrypted for calls during service registration and discovery. This protects your services from being discovered by unauthorized applications.

  • The shared service registry of EDAS is fully integrated with other EDAS components to provide you with a comprehensive microservices solution.

  Operations

  When you create or deploy a Kubernetes application, clear Use the service registry configured for the application. This way, the URL of the Nacos service registry specified in the application configurations will be overwritten by the URL of the shared service registry of EDAS.

• Use an MSE-managed or a self-managed Nacos service registry

  Operations

  When you create or deploy a Kubernetes application, select Use the service registry configured for the application. To prevent the URL of the configured Nacos service registry from being overwritten by the URL of the shared service registry of EDAS during application deployment, EDAS adds the following settings to the application configurations. This ensures that your application uses the service registry that is specified in the application configurations.

  Note

  • Make sure that the service registry that is specified in the application configurations can connect to the application deployed in EDAS. For example, the service registry resides in the same virtual private cloud (VPC) as the application.

  • Nacos 2.X does not support access from all regions. Therefore, your client cannot connect to port 9848.

  • For more information about how to specify Use the service registry configured for the application, see Configure microservices governance.

  -Dnacos.use.endpoint.parsing.rule=false
  -Dnacos.use.cloud.namespace.parsing=false

Use Eureka or ZooKeeper

You can use an MSE-managed or a self-managed Eureka or ZooKeeper service registry. For more information about Microservice Engine (MSE) and the benefits of MSE-managed service registries, see What is MSE?.

Operations

When you create or deploy a Kubernetes application in the EDAS console by using a Eureka or ZooKeeper service registry, select Use the service registry configured for the application. For more information about how to perform the operations, see Configure microservices governance.

You can also change Eureka or ZooKeeper to Nacos in the application configurations to use the shared service registry of EDAS.

Use other types of service registries

If you want to use a service registry of other types, such as Consul, the service registry must be self-managed.

Operations

When you create or deploy a Kubernetes application in the EDAS console by using a service registry of another type, select Use the service registry configured for the application. For more information about how to perform the operations, see Configure microservices governance.

You can also change this type of service registry to Nacos in the application configurations to use the shared service registry of EDAS.

FAQ

Why is the HTTP 403 status code displayed when I connect to the shared service registry of EDAS?

The authentication information of an EDAS tenant will be injected into EDAS. Authentication by using the username and password method has a higher priority than authentication by using the tenant information. Therefore, you must remove the username and password configured for the service registry in the application configurations.

How do I connect to the MSE Nacos service registry?

To connect to the MSE Nacos service registry, perform the following operations: Associate the MSE service registry with an MSE Nacos instance when you create a microservice namespace. Then, select this microservice namespace when you create an application. For more information about how to create a microservice namespace, see Create a microservice namespace.

How do I read the configurations of the shared service registry in my code when I use the shared service registry?

Application Configuration Management (ACM) that is integrated with EDAS is not affected after ACM is discontinued. For more information about how to write code, see Create and dynamically adjust configuration values.