API gateway/proxy pattern for microservices deployed using Azure Service Fabric

Question

After watching the BUILD conference videos for Azure Service Fabric, I\'m left imagining how this might be a good fit for our current microservice-based architecture. There is o

Answer 1

When a service is started, it registers it's endpoint with the fabric naming service. Using the Fabric client APIs you can then ask fabric for the registered endpoints, associated with the registered service name.

So yes, just as you described your case, you would have a gateway that would accept an incoming URI for connection, and then use that path information as the service name lookup, to then create a proxy connection between the incoming request and the actual internal endpoint location.

Looks like the team as posted one the samples that shows how to do this: https://github.com/Azure/servicefabric-samples/tree/master/samples/Services/VS2015/WordCount