Most of my experience with F5 BIG-IP Virtual Edition has been around deploying it in virtualized setups for application load balancing, traffic management, and security use cases, supporting critical systems rather than just testing or labs. I have primarily used it in production and virtual environments.
We have a lot of internally hosted applications for our internal team members across the board, and F5 BIG-IP Virtual Edition has helped us with that. All of these are very big infrastructure, very big environments. We have deployed it as the primary load balancer in front of multiple application servers to distribute traffic evenly, handle SSL offloading to reduce server load, and also to monitor application health and automatically fail over unhealthy instances.
In our environment, F5 BIG-IP Virtual Edition is deployed as a virtual appliance within our virtualization platform. It sat in front of our core web applications and backend services, acting as the primary load balancer and traffic management, especially in the traffic management layer. We have configured it in a HA setup to avoid single points of failure. It handled SSL termination and distributed traffic. From a network perspective, it was placed in a segmented zone between the external facing layer and the internal servers, ensuring controlled and secure traffic flow.
We are using VMware supporting our internal and customer-facing applications for the deployment of F5 BIG-IP Virtual Edition.