Azure Application Gateway vs. F5 Distributed Cloud DNS

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

Probably less appropriate for smaller, very small IT departments, but more suited like when you're doing migrations to the cloud. If it is going to be doing setups for DNS within the cloud, this will let you help you set it up so there's no loss of communication between the two.

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

• I think probably the UI, it's very easily you could scan through and select what you're going to do, and it's kind of similar of the functionality when you compare it to say the Oracle Cloud. So you can go side by side with the windows and then just go through these level when you're going to sell like a new DNS or a new opening on that.

Incentivized

• More cost-effective pricing plans are welcome for the future, especially for WAF
• Ability to automate the TLS certificate renewal procedure
• Ability to manage non-HTTP traffic

Incentivized

• Probably more like AI suggested customizations, like when you do something and then have something like in the background of the AI. When you start doing something, it'll show you what you previously have done and then you could select, you wouldn't have to go through the whole steps over again. It'll say this is what you've done before, do you want to do a copy? And then just modify a couple of things so you don't have to go through the whole process.

Incentivized

Most of the Application Gateway's features and services can be managed and re-configured via either the Azure Portal GUI or via the Azure Cloud Shell, thus allowing both CLI modes, i.e. Azure CLI (Bash) and Azure Powershell. The v2 version of Application Gateway has significantly improved performance during initial configuration or during re-configuration changes, thus making it much more usable for IT admins, as compared to v1.

Incentivized

Very user friendly.

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

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

• Positive : Improved performance and scalability
• Positive : Better and enhanced Security
• Positive : Efficiency
• Negative: Cost
• Negative: More resources to manage.

Incentivized

• I guess positive because we know when we're going to open up, say a DNS or anything, or we're going to have to set something up. We can do it quick and fast instead of having to wait longer for the different steps of how we used to do it before.

Incentivized