AGW and SLB comparison update #127730
AGW and SLB comparison update #127730
Conversation
Added details about Azure Application Gateway and Azure Load Balancer
prmerger-automator
bot
requested review from
AbdullahBell,
cherylmc and
mbender-ms
|
@jaesoni : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
prmerger-automator
bot
added
azure-application-gateway/svc
Change sent to author
labels
|
Learn Build status updates of commit 05bbe8c: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 92d7eb0: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull Request Overview
Updates Azure Application Gateway documentation to include a detailed comparison between Azure Application Gateway and Azure Load Balancer, highlighting their distinct capabilities and use cases for TCP/TLS proxy configurations.
- Added comprehensive feature comparison sections for both Azure Application Gateway and Azure Load Balancer
- Updated the document date to reflect current content
- Enhanced technical details about protocols, scaling, security, and backend connectivity options
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
| 1. **Type** – Layer-4 terminating proxy. | ||
| 2. **Protocols** – Supports TCP or TLS protocols. | ||
| 3. **Versatility** – Use a single endpoint (frontend IP) to serve HTTP and non-HTTP workloads. | ||
| 4. **Scaling** – Configure autoscaling (up to 125 instances) to server your TCP and TLS traffic. |
There was a problem hiding this comment.
| 4. **Scaling** – Configure autoscaling (up to 125 instances) to server your TCP and TLS traffic. | |
| 4. **Scaling** – Configure autoscaling (up to 125 instances) to serve your TCP and TLS traffic. |
@jaesoni Please accept this change, then we can merge. Thanks!
| 3. **Performance** – Provides low latency and high throughput. Built for millions of simultaneous connections with microsecond-level latency. | ||
| 4. **Scaling** – Handles long-lived connections and scales up to millions of flows for all TCP and UDP applications. | ||
| 5. **Inbound and outbound** – Azure Load Balancer delivers complete traffic control with both inbound and outbound capabilities. Seamlessly connect external clients to your applications, while enabling your backend instances to securely reach the internet and other services. | ||
| 6. **Direct server return** - For the return traffic, the backend instance sends the response packet directly back to the client's IP address. |
There was a problem hiding this comment.
| 6. **Direct server return** - For the return traffic, the backend instance sends the response packet directly back to the client's IP address. | |
| 6. **Direct server return** - For the return traffic, the backend instance sends the response packet directly back to the client's IP address, reducing latency and improving performance. |
@jaesoni Please accept this change, then we can merge. Thanks!
There was a problem hiding this comment.
@jaesoni Please accept these change, then we can merge. Thanks!
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
|
Thanks @mbender-ms for the suggestions. Accepted both |
|
Learn Build status updates of commit f77cb7a: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit d4d628e: ✅ Validation status: passed
For more details, please refer to the build report. |
3 participants
Added details about Azure Application Gateway and Azure Load Balancer