Load Balancer Enterprise ADC

I am utilizing the cloud version of LoadBalancer Enterprise  currently, as I have done the deployment in AWS  Cloud, Azure  Cloud, and Google Cloud  as well. I am using all types of cloud, having done private cloud implementations for our environment and public cloud environments with AWS , Google, and Azure .

I utilize LoadBalancer Enterprise 's SSL Termination feature, and options are available to do SSL Termination both in the cloud and in the F5. I have successfully used the SSL Termination feature in F5.

The Advanced Health Check feature in LoadBalancer Enterprise is available, and it has helped in maintaining optimal server performance.

Performance-wise with LoadBalancer Enterprise, I haven't seen any issues between on-premises and the cloud. If there are any performance-related issues, I have the option to automatically upgrade and increase the instances, memory, and CPU configurations. I never come across any performance-related issues in the cloud environment.

When evaluating LoadBalancer Enterprise's application level monitoring, it is similar to the on-premises monitoring capabilities. Additionally, the instance level monitoring is taken care of by AWS Cloud, which continuously monitors CPU, memory, and network usage, sending status updates to the operations teams. Compared to on-premises monitoring, I find the AWS Cloud setup beneficial, as it allows for immediate upgrades when alerts are raised for high CPU utilization, which is a significant advantage.

The intuitive interface of LoadBalancer Enterprise assists me with monitoring network traffic, including options to monitor the network queue and throughput effectively.

Among the best features in LoadBalancer Enterprise, I note that some features are still not enabled compared to the on-premises environment. For example, if I want to deploy certain web policies, I am unsure if they are currently enabled. There are some parameters and configurations, such as persistent configurations, that were not available. I could only host limited applications like HTTPS and HTTP; some complex applications were not supported, and I faced these issues a few years ago. Recently, I have not done any cloud migrations, but I can see that I am now able to migrate most applications. However, some persistent-related configurations were not working, and I am uncertain whether they have solved that issue. These were the major challenges I have encountered.

I have been using LoadBalancer Enterprise in the enterprise environment for almost more than twenty years.

I have communicated with LoadBalancer technical support when facing licensing issues, particularly when needing to move licenses to different instances. When I request the release of the license from the old device, they usually respond appropriately. I can expect a response within fifteen to twenty minutes after I put in a ticket to release the license. While their support is good, the ongoing need to contact F5 for license releases can be a problem from an operational perspective, causing loss of production time, which is a disadvantage I see.

Based on my experience with LoadBalancer Enterprise support, I would rate their responsiveness for releasing licenses a ten. For supporting other aspects, I would give them a rating of six or seven.

I did face challenges when implementing LoadBalancer Enterprise in the cloud environment, as it is not quite easy. There were multiple options available, such as bring your own license and purchasing from the market. I needed to do a deep analysis to determine which option was suitable for the client based on their requirements. Some clients decided to purchase licenses from a vendor, while others chose to use BYOL. For scenarios such as the DR environment, I would only be testing during the DR test period, after which I would shut down these instances. For that need, I chose to go with the marketplace. Some clients wanted continuous production, so I opted for the bring your own license model, as purchasing from the marketplace might cost more. I have faced a couple of ways to choose the license for installation, and initially, the setup and configuration were a bit difficult to handle. After the first device installation, I managed to document what I needed for deployment, making subsequent implementations easier for me.

The approximate timeframes to implement LoadBalancer Enterprise's solution begin with the initial implementations, which can bring up the box in a couple of hours. After that, if there are any migrations or if I'm migrating applications from my own environment to the cloud, that is going to take a lot of time; it cannot be done immediately. I need to work with the backend applications team to bring up those applications, migrate my configurations from on-prem to cloud, verify it, and work with the network team to ensure reachability. During the cutover, I need to shift traffic from on-prem to the cloud, which is a lengthy process. The initial deployment of LoadBalancer Enterprise can be done in a couple of hours, making it live is achievable within that timeframe.

In the deployment of LoadBalancer Enterprise, multiple teams are usually involved for setting up the entire system, as I need an AWS Cloud team, applications team, database team, and security team to facilitate all migrations. However, for deployment purposes, one team is sufficient; in my case, I had three to four engineers. For smaller migrations, I can handle it with one engineer, but for a larger installation of LoadBalancer Enterprise with fifteen to twenty load balancers, one engineer suffices, whereas for migrating one hundred or two hundred, that is when more engineers might be needed.

Regarding the pricing of LoadBalancer Enterprise, I only pay for a license, and whatever license I use doesn't require the same CAPEX investment as physical hardware. I purchase the license depending on my needs. Bring your own license might involve a significant expenditure, whereas the marketplace provides advantages such as the ability to release the license if I'm not using it. When devices are brought back online, I can get the license through the marketplace easily. This system allows me to store snapshots of configuration settings in cloud storage, releasing instances and licenses as needed. Overall, these features highlight the benefits of using LoadBalancer Enterprise compared to on-premises equipment, though I remain unsure of the backend costs associated with the cloud solution.

I do participate in the deployment process of LoadBalancer Enterprise. I would rate this review a nine overall.

My main use case for LoadBalancer Enterprise  involves non-functional testing such as load testing and break-even point validation for our APIs and UIs. I use LoadBalancer Enterprise  to simulate real-life traffic data. For example, when 1,000 users are trying to access a particular resource at a particular time, I simulate this using LoadBalancer by increasing and decreasing the number of virtual users to check the amount of load the server can take. I want to ensure that at any given point in time, 10,000 users or 20,000 users can access our software or website without any interruptions. I provide the virtual user numbers and different other parameters such as our server setup, server configuration, and the number of load balancers being used. After providing these specifics, I simulate the real-world scenario and check if the software is able to handle the load.

There are many types of load balancers, such as NGINX , which is a proxy, and those need to be validated with different types of testing. The number of availability and redundancy need to be checked, the health checks of the software need to be validated, and as a load balancer, I need to check how much traffic it is able to handle at a given point in time.

LoadBalancer Enterprise is very useful in the case of a multifaceted software system. For example, when I do not know exactly how many users are going to be using it at a given point in time, LoadBalancer Enterprise ensures that it distributes the load properly so that the system is not broken and it is available for all users seamlessly.

When I say it distributes the load properly, LoadBalancer Enterprise provides several affinity mechanisms such as cookie, resource, IP, and header-based options. For stateful healthcare workflows and banking transactions where session context matters, these options are flexible and reliable. In stateful failover edge cases, I need to make sure it is working properly, and those are the things I need to validate.

LoadBalancer Enterprise simulates production traffic profiles by using a realistic traffic generator that models different requests and transaction mixes such as reads and writes, leveraging replay traffic from sanitized production traces whenever possible. LoadBalancer Enterprise allows me to simulate chaos and failure injection by integrating chaos testing to validate retry and back-off behavior, connection drain, and upstream slowdown scenarios. I can validate that rate limits and circuit breakers are functioning properly.

LoadBalancer Enterprise has given my company the confidence that our software is sustainable and scalable according to our design. I can approach customers with confidence that they will not be facing any issues such as unavailability of services or any interruptions during their work. This confidence gives my company an edge over competitors.

LoadBalancer Enterprise could provide more flexibility in terms of configuration setup, making it more user-friendly when switching between other software.

LoadBalancer Enterprise could work more on content caching by bypassing the back-end server more often and making the cache more accessible so that it gives better and more robust results. The autoscaling integration could be improved as well. DDoS mitigation is helpful, but there are some cases where it does not recognize the threat, so those are areas it could work on.

I have been using LoadBalancer Enterprise for the last three to four years.

I have definitely seen very lesser downtimes after I implemented the different load balancer functionalities. The regular health checks that LoadBalancer Enterprise performs using regular Jenkins  jobs utilize all the functionalities of LoadBalancer Enterprise to make sure everything is working perfectly according to my design. This has given a positive impact to my overall software, which boosts confidence for both me and customers.

LoadBalancer Enterprise is pretty stable.

LoadBalancer Enterprise is very useful in the case of a multifaceted software system. For example, when I do not know exactly how many users are going to be using it at a given point in time, LoadBalancer Enterprise ensures that it distributes the load properly so that the system is not broken and it is available for all users seamlessly.

Previously, I was using Kafka, and I wanted a more scalable, robust, and synchronous setup for my software. I switched to LoadBalancer Enterprise because the buffer time in Kafka was very high, and it is synchronous. The event ingestion and message queuing were not optimized, so I switched to LoadBalancer Enterprise.

LoadBalancer Enterprise has optimized my traffic by about 20 to 30%. There are very lesser downtimes in terms of my overall data, including software deployment, development, and testing cycles. LoadBalancer Enterprise has drastically improved my productivity. The overall improvement is about 30%.

I purchased LoadBalancer Enterprise through the AWS  marketplace. With the licensing and setup cost, I think it is pretty good, but the overall cost is not something I am aware of. That is handled by the DevOps team, so I am not sure about that.

LoadBalancer Enterprise is very useful, and I believe others should go for it. Obviously, it is the call of the DevOps team and the overall system designers and architects to make a decision. However, comparing it with other tools, LoadBalancer Enterprise is pretty solid in terms of distributing workloads, so you can go ahead. I would rate this product an 8.