helidon
helidon copied to clipboard
Published
20 hours ago •
helidon-io
helidon-io
Investigate service registry integrations
Find out what kind of support we could provide in Helidon for integration with service registries
- Discover registries used in industry (e.g. Consul, Eureka)
- Find out what kind of information is needed to register a service
- Find out if we can/should integrate client calls with such a registry
- Add tasks for identified (and desired) features in Helidon
@tomas-langer Thanks for creating a new issue. My 2¢:
- Ideally, the config should support providing e.g. Consul cluster coordinates and the API for service registry should be enhanced to automatically register with the service discovery cluster.
- I guess the health checks can also be integrated with e.g. Consul health checks.
- Another useful feature of Consul is the distributed config so enhancing the config functionality to fetch properties from Consul would be great (see https://www.consul.io/api/kv.html). Also requested in another issue, see #404.
This topic we are still actively pursuing? Are we looking to add some libraries to enable Eureka in Helidon?
@pallabrath we are not actively working on this issue, as we have higher priority issues to handle.
Step one will be to understand the requirements involved.
For abstract purposes:
- What is a service registry in this usage of the word? (Yes, I know, Eureka and Consul and Kubernetes and Spring and so on but we are Helidon so what does it mean to us and what does it look like generically? What capabilities does it "serve" and what "services" does it "register" and to what end?)
- If we are looking to "integrate" in some fashion with several kinds of service registries, whatever they are, what is the lowest common denominator they all have in common that we should expose? What should they "look like" to our end users in whatever way it is that Helidon "shows" them to them? (My initial uninformed bias is: this is a problem for Kubernetes and its ilk to solve directly.)
