You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@dubbo.apache.org by "Huxing Zhang (JIRA)" <ji...@apache.org> on 2019/03/25 02:14:00 UTC

[jira] [Resolved] (DUBBO-35) GSoC 2019: Consul as one of Dubbo's Service Discovery solution.

     [ https://issues.apache.org/jira/browse/DUBBO-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Huxing Zhang resolved DUBBO-35.
-------------------------------
    Resolution: Fixed

> GSoC 2019: Consul as one of Dubbo's Service Discovery solution.
> ---------------------------------------------------------------
>
>                 Key: DUBBO-35
>                 URL: https://issues.apache.org/jira/browse/DUBBO-35
>             Project: Apache Dubbo
>          Issue Type: Task
>            Reporter: Jun Liu
>            Priority: Major
>              Labels: GSoC2019
>
> Dubbo has a well-defined [Service Directory|https://vaadin.com/blog/microservices-service-registration-and-discovery] SPI to integrate with Registry Servers. It's very easy to integrate with various registry servers by following the SPI interfaces and conventions. Below are the servers supported by Dubbo:
> * Zookeeper
> * Redis
> * Multicast
> * Etcd
> [Consul](https://www.consul.io/) has emerged as a popular Service Directory solution for microservices, so I think it should also be included as a solution in Dubbo's kit.
> Here is the related SPI definition you may need to extend:
> * Registry
> * RegistryService
> * RegistryFactory



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)