Given the gateway is a reverse proxy, support for a wide range of TLS scenarios is critical. We ran our production scenarios on all 3 webservers, and we realized it all came down to TLS support. When we started the porting effort, the first question we had to ask ourselves was which of the 3 webservers in. NET Framework 4.6.2 (effectively doubling our throughput).Īs a result of the gains in throughput, we were able to reduce our fleet size from ~40k cores to ~20k cores (50% reduction). The image below shows that our CPU usage was reduced by half on. In Azure AD gateway’s case, we were able to cut our CPU costs by 50%. NET Core performance translate to real-life cost savings? NET Core and the results made the decision very easy: we must port our service to. We ran our own benchmarks on gateway prototypes on. NET Core’s focus on performance caught our attention, especially since TechEmpower listed ASP.NET Core as one of the fastest web frameworks on the planet. Finding ways to reduce the cost of executing the service has been a key goal for the team behind it. The gateway’s scale of execution results in significant consumption of compute resources, which in turn costs money.
Up until recently, Azure AD’s gateway was running on. The gateway is present in more than 53 Azure datacenters worldwide and serves ~115 Billion requests each day.
The gateway provides features such as TLS termination, automatic failovers/retries, geo-proximity routing, throttling, and tarpitting to services in Azure AD.
If you’ve used services such as, , or, then you’ve used Azure AD’s gateway. Azure Active Directory’s gateway service is a reverse proxy that fronts hundreds of services that make up Azure Active Directory (Azure AD).