What's the built-in way for Micro-service Service Registry and Service Discovery in Azure Kubernetes and Azure Service Fabric? I got reference to below service registries.
- Apache Zookeeper
- Consul
- Etcd
Are they compatible to use in Azure environment? Any leads here for dynamically discover container based Micro-services deployed in AKS and ASF, under a single node? Azure API Management https calls may not be a best option for inter service communication inside a single node, it may be good option for external clients though
You should not try to reinvent the wheel, unless there are some specific features in these products that you want but didn't disclose in your original answer.
Kubernetes and Service Fabric, both provides a simple and useful feature for service discovery, called DNS Service.
Whenever new services are created, they are registered in the DNS with their addresses, when an application running on the cluster tries to resolve a DNS for a particular service domain name, it query the DNS and get the IP of the service without you requiring to type any additional logic other than the out of the box provided by most languages.
Service Fabric, also provides two other features for service discovery if for example you need to resolve stateful services and need get a specific partition:
Kubernetes on the other hand, does not provide baked features the same way, because it is more flexible to chose your own solution, in this case, there are plenty of solutions out there. One I can guide you to is Istio