Skip to main content

Comparison between Azure Application Gateway V1 and V2

Microsoft has announced new version of Azure Application Gateway and its Web Application Firewall module (WAF). In this article, we will discuss about the enhancements and new highlights that are available in the new SKUs i.e. Standard_v2 and WAF_v2.




Enhancements and new features:

Scalability: It allows you to perform scaling of the number of instances on the traffic.
Static VIP: The VIP assigned to the Application Gateway can be static which will not change over its lifecycle.
Header Rewrite: It allows you to add, remove or update HTTP request and response headers on application gateway.
Zone redundancy: It enables application gateway to survive zonal failures which allows increasing the resilience of applications.
Improved Performance: Improvement in performance during the provisioning and during the configuration update activities.
Cost: V2 SKU may work out to be overall cheaper for you relative to V1 SKU. For more information, refer Microsoft pricing page on V2 SKU costs.

The below table shows the comparison between Application gateway V1 and Application Gateway V2:

Features
v1 SKU
v2 SKU
Autoscaling

Zone redundancy

Static VIP

Azure Kubernetes Service (AKS) Ingress controller

Azure Key Vault integration

Rewrite HTTP(S) headers

URL-based routing
Multiple-site hosting
Traffic redirection
Web Application Firewall (WAF)
WAF custom rules

Transport Layer Security (TLS)/Secure Sockets Layer (SSL) termination
End-to-end TLS encryption
Session affinity
Custom error pages
WebSocket support
HTTP/2 support
Connection draining

Microsoft will disable the creation of new Application gateway on V1 SKU soon. So, you may refer this article: https://docs.microsoft.com/en-us/azure/application-gateway/migrate-v1-v2 to migrate your existing Application gateway V1 to V2.


Comments

  1. This was huge information for all ,those who needed these type article. This was really good and of course knowledgeable. Thank you for sharing this much information with us.Azure Synapse Analytics

    ReplyDelete
  2. Share great information about your blog , Blog really helpful for us . IT Support in Logan

    ReplyDelete
  3. You've shared some excellent material. I'm grateful for this post because it contains a lot of useful information Mexico Export Data.Thank you for sharing this piece of writing.

    ReplyDelete
  4. Impressive and powerful suggestion by the author of this blog are really helpful to me.
    Vonex NBN

    ReplyDelete
  5. This comment has been removed by the author.

    ReplyDelete
  6. This comment has been removed by the author.

    ReplyDelete
  7. I read your blog now share great information here.
    levitra comprar

    ReplyDelete
  8. Data eSim Card for Travel is a new way to travel that's faster, easier, and more secure. With it, you can travel without carrying any physical cards or passports. Instead, use your data eSim card to access your travel information and make your travel reservations.

    ReplyDelete

Post a Comment

Thanks for your comment. In case of any concerns, please contact me at er.ashishsharma@outlook.com

Popular posts from this blog

Difference between Azure Front Door Service and Traffic Manager

Azure Front Door Service is Microsoft’s highly available and scalable web application acceleration platform and global HTTP(s) load balancer. Azure Front Door Service supports Dynamic Site Acceleration (DSA), SSL offloading and end to end SSL, Web Application Firewall, cookie-based session affinity, URL path-based routing, free certificates and multiple domain management. In this article, I will compare Azure Front Door to Azure Traffic Manager in terms of performance and functionality. Similarity: Azure Front Door service can be compared to Azure Traffic Manager in a way that this also provides global HTTP load balancing to distribute traffic across different Azure regions, cloud providers or even with your on-premises. Both AFD & Traffic Manager support: Multi-geo redundancy: If one region goes down, traffic routes to the closest region without any intervention. Closest region routing: Traffic is automatically routed to the closest region. Differences: Azu

Install Solr as an Azure App Service

After Sitecore 9.0.2, Solr is a supported search technology for Sitecore Azure PAAS deployments. In this article, we will install SOLR service 8.4.0 in Azure App Service for Sitecore 10. 1. Create Azure App Service Login to Azure and create Azure App service. Make sure Runtime stack should be Java. 2. Download Solr Download Solr 8.4.0 from https://archive.apache.org/dist/lucene/solr/ Extract the files and add the below web.config file in the Solr package. <?xml version="1.0" encoding="UTF-8"?> <configuration>  <system.webServer>      <handlers>      <add  name="httpPlatformHandler"            path="*"            verb="*"            modules="httpPlatformHandler"            resourceType="Unspecified" />    </handlers>    <httpPlatform processPath="%HOME%\site\wwwroot\bin\solr.cmd"        arguments="start -p %HTTP_PLATFORM_PORT%"

Azure Blob storage - Last access time tracking now generally available

Azure service updates Azure Blob storage - Last access time tracking now generally available This feature helps administrators control costs through the automatic tiering and deletion of blobs via tiering including when the data was last read. Click here for more information.

Azure Machine Learning public preview announcement //Build, May 2021

Azure service updates Azure Machine Learning public preview announcement //Build, May 2021 New feature: Prebuilt Docker images for Inferencing, now in public preview. Click here for more information.