F5 BIG-IP Local Traffic Manager (LTM) vs. VMware NSX

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

With proper design, VMware NSX can and should be deployed to virtually any VMware virtualization environment, but the deployment should be tailored to the needs of that environment. There isn't really a one size fits all deployment design for all environments. That versatility is what provides its greatest strength to a business.

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

• End to end encryption on the wire.
• Micro-segmentation.
• Integrates well with existing VMWare environment.
• Integrates well with our existing network.

Incentivized

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

Incentivized

• Interoperability in multi-vendor environments
• Advanced networking and packet acceleration options can be improved

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

We use both Cisco ACI and VMware NSX, and while they have different strengths and capabilities, I would recommend VMware NSX, as it can be used in all VMware environments, without costly physical infrastructure changes. Cisco ACI provides some of the same capabilities, but not all. It's focus relies on physical networking changes.

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

• Ability to move workloads more easily with the ability to stretch/move networks across multiple physical locations.
• The added flexibility allows you to expedite tech refreshes since you're no longer constrained by the hardware.

Incentivized