Skip to main content

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:

  1. Multi-geo redundancy: If one region goes down, traffic routes to the closest region without any intervention.

  2. Closest region routing: Traffic is automatically routed to the closest region.



Differences:

  1. Azure Front Door provides TLS protocol termination (SSL offload), and Azure Traffic Manager does not. It means AFDs take load off from the Web Front Ends, which do not have to encrypt or decrypt the request.

  2. Azure Front Door provides application layer processing, and Azure Traffic Manager does not.

  3. While using AFS, user will experience better performance than traffic manager as AFD uses Anycast, which provides lower latency, thereby providing higher performance.

  4. AFD provides WAF feature for your application to provide security from DDoS attacks.

  5. We can perform URL rewriting in Azure Front Door but not in Traffic Manager.

  6. Traffic manager relies on DNS lookup for network routing while AFD uses reverse proxy which provides faster failover support.

  7. AFD caches the static content while no caching mechanism is available in Traffic Manager.



Quick Summary:


Azure Front DoorTraffic Manager
Cross region redirection & availability.Cross region redirection & availability.
SSL offloadNo SSL offload
Uses Reverse proxyUses DNS lookup
Caches static contentNo caching available
Uses AnyCast & Split TCPDoes not use such service
AFD provides WAF featureNo such feature
99.99% SLA99.99% SLA

I hope this information helped you. In our next article, we will discuss how to create and use Azure Front Door service.

Popular posts from this blog

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 prici

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.

Configure Sitecore Publishing Service in Azure App Service

In this article, we will set up and configure Sitecore Publishing Service in Azure App Service. 1. Download Publishing service & module You can download from dev.sitecore.com. Sitecore Publishing Service : It is an opt-in module providing an alternative to the default Sitecore publishing mechanism, focusing on increased performance by doing operations in bulk. I have downloaded "Sitecore Publishing Service 4.3.0". Sitecore Publishing Service Module : It provides integration with the opt-in Publishing Service, supporting high-performance publishing in large scale Sitecore setups.   2. Install & Configure publishing service in Azure App Service 2.1 Create Azure App service. Once the App Service is created, open Kudu & navigate to Debug Consule -> CMD . Navigate to site\wwwroot folder. Drag & Drop zip folder “ Sitecore Publishing Service 4.3.0-win-x64.zip ” to kudu folder view area. You can unzip the folder using below command. unzip -o *.zip 2.