Skip to content

Commit 0b17803

Browse files
Merge pull request #267774 from jaesoni/slv-vs-appgw
Clarification on SLB vs AGW
2 parents 7f0d67b + b7f67ef commit 0b17803

File tree

1 file changed

+9
-2
lines changed

1 file changed

+9
-2
lines changed

articles/application-gateway/tcp-tls-proxy-overview.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.author: greglin
1313

1414
In addition to the existing Layer 7 capabilities (HTTP, HTTPS, WebSockets and HTTP/2), Azure Application Gateway now also supports Layer 4 (TCP protocol) and TLS (Transport Layer Security) proxying. This feature is currently in public preview. To preview this feature, see [Register to the preview](how-to-tcp-tls-proxy.md#register-to-the-preview).
1515

16-
## Application Gateway Layer 4 capabilities
16+
## TLS/TCP proxy capabilities on Application Gateway
1717

1818
As a reverse proxy service, the Layer 4 operations of Application Gateway work similar to its Layer 7 proxy operations. A client establishes a TCP connection with Application Gateway, and Application Gateway itself initiates a new TCP connection to a backend server from the backend pool. The following figure shows typical operation.
1919

@@ -24,7 +24,14 @@ Process flow:
2424
1. A client initiates a TCP or TLS connection with the application gateway using its frontend listener's IP address and port number. This establishes the frontend connection. Once the connection is established, the client sends a request using the required application layer protocol.
2525
2. The application gateway establishes a new connection with one of the backend targets from the associated backend pool (forming the backend connection) and sends the client request to that backend server.
2626
3. The response from the backend server is sent back to the client by the application gateway.
27-
4. The same frontend TCP connection is used for subsequent requests from the client unless the TCP idle timeout closes that connection.
27+
4. The same frontend TCP connection is used for subsequent requests from the client unless the TCP idle timeout closes that connection.
28+
29+
### Comparing Azure Load Balancer with Azure Application Gateway:
30+
| Product | Type |
31+
| ---------- | ---------- |
32+
| [**Azure Load Balancer**](../load-balancer/load-balancer-overview.md) | A pass-through load balancer where a client directly establishes a connection with a backend server selected by the Load Balancer's distribution algorithm. |
33+
| **Azure Application Gateway** | Terminating load balancer where a client directly establishes a connection with Application Gateway and a separate connection is initiated with a backend server selected by Application Gateway's distribution algorithm. |
34+
2835

2936
## Features
3037

0 commit comments

Comments
 (0)