title: Why should I use the Service Fabric Reverse Proxy instead of the Azure App Gateway to talk to SF Cluster?
body: <p>It's a long question and there are trade-offs, I'm sure.  The documentation in this <a href="https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-reverseproxy" rel="noreferrer">area</a>:</p>
  
  <p><strong>Doesn't</strong> give me enough to answer the question above confidently.  </p>
  
  <p>So, they say: 
  "Azure Application Gateway (AG) attempts to resolve a service address again and retry the request when a service cannot be reached". </p>
  
  <p>I know how the Service Fabric Reverse Proxy (RP) does this by encapsulating the resolve loop. Does the AG have this capability too?  The AG is a reverse proxy too, by all accounts.</p>
  
  <p>So, crucially for <strong>external</strong> traffic into a SF cluster, why would I use one over another  (I am aware that the RP allows intra-cluster comms too and this is a good fit). </p>