The API Management instance is meant to allow you to manage external access to your APIs, Functions, etc. hosted on Azure or on-premises environment, as long as you ensure connectivity between your Azure tenancy and your on-premises environment. The Service Fabric Gateway Service and Reverse Proxy Service are meant to manage exclusively the communication of your Service Fabric cluster. So, by using the Service Fabric Reverse Proxy, it is possible for a gateway service to intercept the traffic and forward it to the relevant service type in Service Fabric Reverse Proxy. Then the proxy is able to handle the complexity in finding the relevant container location and address to forward the incoming traffic.
So, to summarize, the API Management is meant to manage access control, apply policies and more for most of your applications hosted in Azure that have external users or apps accessing it. And the SF Gateway and Reverse Proxy is dedicated to Service Fabric, but these services do not manage access control. That's managed on your Access Control List, please see this article for more information.
Last, but not least, in case your service fabric application has external users accessing it, i would recommend you to consider to integrate API Management with your Service Fabric cluster, see more here .
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.