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

I am wondering instead of exposing Rest at N+ services, use the default comm stack everywhere inside service fabric (or as much as possible to keep thing simple internally). Expose REST only at the edge entry point(s) into the fabric. Use a std stateless web 2.x api which wraps the fabric proxies of your services and actors, and/or use a fabric service exposing rest in the same way. Aggregate your apis as needed in the forward facing Rest service(s). Not sure I seen the need yet for additional overhead of an aggregator for naming redirection (maybe I am missing the thought). Then it would seem just an exercise in organizing (and securing) rest endpoint(s) with a desired namespace (i.e. façade pattern).