Azure Front Door
Applications need to improve performance, scale their application, enable instant failover, or enable complex application architectures like IaaS and PaaS, on-prem + cloud, or multi-cloud hybrid experiences. Adding AFD in front of your application or API you will fill improvements and optimizations at the edge such as TCP Fast Open, WAN optimizations, and improvements to SSL such as SSL session resumption.
AFD is a scalable and secure entry point for the fast delivery of your global applications. AFD is your one-stop solution for your global website/application and provides the following feature:
AFD is a scalable and secure entry point for the fast delivery of your global applications. AFD is your one-stop solution for your global website/application and provides the following feature:
- AFD built on world-class Microsoft Global Network infrastructure. Always keep your traffic on the best path to your app, improve your service scale, reduce latency and increase throughput for your global users with edge load balancing and application acceleration.
- SSL offload and application acceleration at the edge close to end-users
- Global HTTP load balancing with instant failover
- Actionable insights about your users and back ends
- Web Application Firewall (WAF) and DDoS Protection
- The central control plane for traffic orchestration
Most Popular AFD Features:
- Globally distributed microservice applications
- Dynamic applications with global reach
- Global, real-time performance and availability for your app or API
- Scale up your global application
- Protect your app from attacks
- Centralized traffic orchestration view
Credit: https://azure.microsoft.com/ |
Azure Traffic Manager
Domain Name System(DNS)-based traffic load balancer that enables to distribute traffic optimally to services across global Azure regions while providing high availability and responsiveness.Traffic Manager uses DNS to direct client requests to the most appropriate service endpoint based on a traffic-routing method and the health of the endpoints. Followings are the most popular feature:
- Increase application availability
- Improve application performance
- Perform service maintenance without downtime
- Combine hybrid applications
- Distribute traffic for complex deployments
Traffic-routing method
- Priority: Best to use when you need to use a primary service endpoint for all traffic, and provide backups in case the primary or the backup endpoints are unavailable.
- Weighted: Best to use when you need to distribute traffic across a set of endpoints, either evenly or according to weights, which you define.
- Performance: Best to use when you need to have endpoints in different geographic locations and you want end users to use the "closest" endpoint in terms of the lowest network latency.
- Geographic: user's shall be directed to specific endpoints (Azure, External, or Nested) based on which geographic location their DNS query originates from. Examples include complying with data sovereignty mandates, localization of content & user experience and measuring traffic from different regions.
- Multivalue: Select MultiValue for Traffic Manager profiles that can only have IPv4/IPv6 addresses as endpoints. When a query is received for this profile, all healthy endpoints are returned.
- Subnet: Select Subnet traffic-routing method to map sets of end-user IP address ranges to a specific endpoint within a Traffic Manager profile. When a request is received, the endpoint returned will be the one mapped for that request’s source IP address.
Credit: https://docs.microsoft.com |
Comments
Post a Comment