Azure Application Gateway with Service Fabric

Question

I currently have a Service Fabric cluster with two stateless services that support the Asp Web API. When creating the cluster, the corresponding Azure load balancers were also created.

Now I would like to add an Application Gateway in front of my cluster for various reasons, such as SSL offloading, URL routing, etc.

I would like to understand how to properly configure the application gateway. I see 2 options, I don’t know which one is valid:

• Application Gateway replaces the existing load balancer and points directly to the SF services hosting WebApi
• I keep the existing LB configuration and the gateway points of the application to this LB (there seem to be too many 1 LB solutions)

Which one is correct? Any tuning tips?

Answer 1

Approach 2 is what we use. We have saved the load balancer and route any request received from the application gateway. We found this to be the easiest and easiest choice, as it is due to the minimal changes that need to be made to the Application Gateway.

Answer 2

Your two web api can run on each node in the VM scale set. Azure load balance is used to distribute traffic across these nodes. Orienting one service to one node will reduce scalability and fault tolerance.

You can use the App Gateway to translate the incoming request to different ports on the load balancer. (For example, direct traffic to API 1 @url ~ / 1 / and API 2 @url ~ / 2 /)

Use load balancing rules (using all nodes) for NAT redirection (for individual nodes). Thus, you get a reliable and reliable system.

Answer 3

Solution 2 would also provide perhaps a VPN connection, for example, to manage your cluster. Then there is no need to disclose the management endpoint to the public. The domestic pound also includes additional features for future use.

Answer 4

I would go with your first option and implement it by creating / modifying your ARM template so that it does not contain a load balancer and instead contains an application gateway.

Here is a link to quick start ARM templates that you can use. There is no example out of the box for the service model with a gateway, but this will give you a great starting place.

link