Azure Application Gateway vs. F5 BIG-IP

For building scalable and highly available applications, Azure Application Gateway does most of the job on behalf of you; automatically load-balancing traffic from a number of users to a number of back-end servers. This ensure scalability and availability. The in-built security is great as can be expected from Microsoft, and user has a variety of tools for monitoring the health of the load-balancing function as well as the health of back end servers behind it.

Incentivized

I really do think it's well suited for any placement on the edge, especially with the WAF portion. APM is a whole different module unto itself that allows for VPN Connect connectivity, web top access. So it really is for these modules anyway, an edge appliance for us and not really usable in the interior of the network.

Incentivized

• Easy integration with Load Balancer and Azure Scale Set to provide a full solution for traffic management.
• With rich routing rule, we could use one Application Gateway as the central point for all internal applications to expose to the external network.

Incentivized

• Easy connection: you can connect to your corporate network with two clicks.
• IP restriction: F5 has a list of possible insecure IP numbers, if someone tries to connect using one of these numbers, F5 BIG-IP won't connect.
• Always on feature: Very handy feature, if you install always on, you won't need to click connect.

Incentivized

• Live examples in the Azure documentation
• Application Gateway UI Blade in Azure Portal can be streamlined
• Have more advanced feature set as WAF (Web Application Firewall)

Incentivized

• I think the policy configuration that had some improvements on the ASM word things, improvements may be on the signatures that would be good because it's a little bit confusing on the ASL, how they are updated and deployed, and this staging. So that's something that could be.

Incentivized

Only way to to this type of tasks

Incentivized

Great customization and easy to use help reference menus

Incentivized

I don’t like that it's part of the Microsoft brand. In general, I am not a fan of Microsoft products but Azure gets it right.

Incentivized

On the occasions when we've had to engage f5 support, they have been great. They have always resolved our issues quickly and been easy to work with and professional. The reason I give them a 10 out of 10, however, is because when we've had issues that have crossed over between the f5 BIG-IP, our Cisco switches, and our Microsoft IIS server the f5 support representatives have been extremely knowledgeable about every product and device involved and have been able to troubleshoot end-to-end without having to engage other vendors.

Incentivized

implementation is fine

Incentivized

Other load balancing tools in Azure (Azure LB and Azure Traffic Manager) are limited in their functionality in comparison with the Azure Application Gateway, and also, they don't provide security features. Azure Firewall, although it has security features, is more expensive, and most importantly, it's not a load balancer at all.

Incentivized

F5 BIG-IP is my first F5 product that I have stared to work, and it brings me more experience doing a lot of migration upgrades from old code version to new code. The way F5 has all configuration help us to develop scrips to improve our process.

Incentivized

• Costs increased for the company, so expenses were more than before.
• Was able to get better user experience so users won't feel the website is useless.

Incentivized

• Having a load balancer of F5 helps to address large traffic limit on organisation's application
• This means that organisation gets a lot of revenue due to the usage of their application
• Hence provide a very positive impact onthe inverment or ROl of the organisation

Incentivized