[
https://issues.apache.org/jira/browse/IGNITE-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saikat Maitra reassigned IGNITE-1204:
-------------------------------------
Assignee: Saikat Maitra
> Cluster Discovery via Consul
> ----------------------------
>
> Key: IGNITE-1204
> URL: https://issues.apache.org/jira/browse/IGNITE-1204
> Project: Ignite
> Issue Type: New Feature
> Components: general
> Reporter: Raúl Kripalani
> Assignee: Saikat Maitra
> Priority: Major
> Labels: discovery
>
> According to [their website|https://www.consul.io/]:
> {quote}
> * Consul makes it simple for services to register themselves and to discover
> other services via a DNS or HTTP interface.
> * Pairing service discovery with health checking prevents routing requests to
> unhealthy hosts and enables services to easily provide circuit breakers.
> * Consul scales to multiple datacenters out of the box with no complicated
> configuration. Look up services in other datacenters, or keep the request
> local.
> * Flexible key/value store for dynamic configuration, feature flagging,
> coordination, leader election and more. Long poll for near-instant
> notification of configuration changes.
> {quote}
> It would be nice to provide cluster discovery via Consul.
> Consul itself is MPL v2 licensed. According to [this ASF
> reference|https://www.apache.org/legal/resolved.html#category-b], this is a
> Category B license meaning that it's not viral by nature but it requires some
> degree of reciprocity. We don't really care much about this, because we won't
> be packaging Consul obviously.
> Moreover, there's a [client on GitHub|https://github.com/Ecwid/consul-api]
> that's ASLv2. Worse comes to worst, we could just invoke the HTTP API
> directly with no dependencies.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
