F5 BIG-IP Local Traffic Manager (LTM) Reviews

Our primary use cases for F5 BIG-IP Local Traffic Manager are high availability for applications and SSL offload certificates.

F5 BIG-IP Local Traffic Manager helps reduce our downtime for maintenance purposes. It also offers us ease of use for the deployment of certificates onto a central location, as opposed to individual nodes.

I basically work for the solutioning only, so I've been migrating the F5 from the existing chassis to the new chassis for the last three years. Before that, I was a part of operations so I was working to support any incidents on F5. 

We have multiple solutions we can deploy through the F5.

The basic load balancing is acting as a round-robin. Other features we can use are based on the application team's requirements. F5 is not only basically giving solutions based on the network background, but it's also compatible based on the application level. Therefore, whenever the application team has a specific requirement, we can tweak it and we can provide the solution over the LTM.

I work for a bank, and we have a mobile banking app with around 25,000 users.  We use LTM for load balancing on the internal network, and the web feature helps us fill holes in application security due to vulnerabilities in legacy applications. 
It also provides perimeter protection against DDoS attacks and SQL injection. 

F5's attack signatures and automation are the most valuable features. The disaster recovery capabilities are also excellent. You don't need to do anything. It has automatic failover from production.

For everything, F5 BIG-IP Local Traffic Manager (LTM) is used. We used it for our exchange server before migrating to Teams, and then for Skype. It currently operates several large broadcasting and streaming services.

Our jump server is quite large. To keep the high number of connections, we had to deploy it behind the F5. That saved us a lot of time and achieved our goal of having a stable jump server. When you put it behind an F5, you divide the connections between a couple of nodes, which was something we didn't have before.

We use it primarily for WAF.

The ability to quickly set up. I understood it very quickly. I had some URLs which pointed to my load balancers, and inside there, I had to send an action to the API Gateway. I thought it was going to be a very complex thing for me to do, but that one rule that I had to create, it solved everything for me.

The connection through the API Gateway worked in no time, which was fantastic. From the perspective of us building it, once you have that one rule you can stamp it out. Also, it was easy for me to show operations, "Look how easy it is. There's nothing complex about it." 

We're offering services to citizens who access them over the internet, and we use F5 BIG-IP Local Traffic Manager (LTM) for load balancing between many physical servers or backend servers.

I like that F5 BIG-IP Local Traffic Manager (LTM) is a product that comes with valuable features, but what stands out from all features is load balancing.

We have deployed it for two customers. One uses the local LTM for load balancing the application. The other uses it as a raft and for load balancing.

F5 is easy to deploy, though more challenging than Kemp. Configuration takes time, but it's stable. It offers features Kemp doesn't provide. For example, there are predefined templates for handling Office 365. You can download them for automatic configuration.