Eureka, ZooKeeper, and Nacos are popular service registry types in Java microservices models. Service registries are used to implement service registration and discovery. They can decouple services and free you from dependency management. This way, you can dynamically manage microservices. This topic describes the service registries supported by Enterprise Distributed Application Service (EDAS) and how to perform O&M for these service registries.

Service registries

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

EDAS provides hosting and microservice governance services for your application, regardless of the type of service registry that your application uses.

注册中心选型

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

Use Nacos

If your application uses a Nacos service registry, the following two O&M methods 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 has 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 complete set of microservice solutions.
    Operations

    When you create or deploy an application, clear Use Configured Registration Center. This way, the URL of the Nacos service registry specified in the application configuration 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 an application, select Use Configured Registration Center. 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 configuration. This ensures that your application uses the service registry specified in the application configuration.

    Note Make sure that the service registry specified in the application configuration can connect to the application deployed in EDAS. For example, the service registry resides in the same virtual private cloud (VPC) as the application.
    -Dnacos.use.endpoint.parsing.rule=false
    -Dnacos.use.cloud.namespace.parsing=false

Use Eureka or ZooKeeper

If your application uses a Eureka or ZooKeeper service registry, you can use an MSE-managed or a self-managed Eureka or ZooKeeper service registry.

Note Make sure that the service registry specified in the application configuration can connect to the application deployed in EDAS. For example, the service registry resides in the same VPC as the application.
Operations

When you create or deploy an application, select Use Configured Registration Center.

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

Use other types of service registries

If your application uses a service registry of another type such as Consul, you must use a self-managed service registry.

Note Make sure that the service registry specified in the application configuration can connect to the application deployed in EDAS. For example, the service registry resides in the same VPC as the application.
Operations

When you create or deploy an application, select Use Configured Registration Center.

You can also change other service registry types to Nacos in the application configuration to use the shared service registry of EDAS.