F5 BIG-IP Local Traffic Manager (LTM) vs. Imperva Application Firewall

There was a need to have the DR environment to be available actively but not to send the traffic unless the production is down The F5 BIG-IP Local Traffic Manager (LTM) priority feature helped achieving it. It was well suited in handling the HTTP headers using polices and iRules. It was less appropriate from the application security perspective in the current version. But after attending the AppWorld 2024, I see a lot of ways to protect the network and the application with several features.

Incentivized

Incapsula as a Web Application Firewall is fantastic and very well priced compared to other products in the market. Load balancing supports management of multiple development and live environments, rewrite rules and behaviour rules to migrate traffic between sites and allow switching between different endpoints. The reporting features allow you too see the level of traffic instantly

Incentivized

• Does web traffic management very well.
• To allow API's to work with our in house services
• To make intelligent load balancing decisions.

Incentivized

• Security
• Reporting
• Oversight
• Redirections
• Rules

Incentivized

• Time investment in creating Virtual Servers across many LTMs
• Ability to change object names after creation
• Support ability to troublshoot iRUles

Incentivized

• The portal has recently been redesigned, finding previous sections will take time to familarise

Incentivized

As far as I know, F5 BIG-IP Local Traffic Manager (LTM) from F5 is the best and the number of features is unmatched compared to its competitors. The first-time setup is also quick and easy and the product behaves as a full proxy which is rarely seen. The support is good and also the help articles are numerous.

Incentivized

When going out to market we reviewed several products to compare. What we discovered was that Incapsula offered the best value and everything that we needed for a business of our size. We are able to "bolt on" bandwidth and functionality as the requirement grows, or scale down if no longer required.

Incentivized

• Negative impact in that it makes it very easy for applications to be spun up but cleanup of old/ unused deployments do not happen causing resources to be consumed unnecessarily
• When used in a multiblade viprion guest, issues with backplane and blade replication causing impact
• Ability to deploy multiple instances helped with network segmentation

Incentivized