F5 BIG-IP Pros and Cons
F5 BIG-IP Pros
I was able to simply and quickly set up the WAF rules and security, and also set up easily complex policies and rules which gave me some great features to redirect.View full review »
It has so many features. First of all, it has a full proxy architecture, it has multiple modules. The best feature is the WAF, the web application firewall module. It also has cashing type capabilities. It has all kinds of load-balancing algorithms based on your IT requirements.
It provides first-tier firewalling, for you application. And it provides server load-balancing, it provides optimization, and it provides a proxy feature, where your users cannot directly access your server. It acts as a fully proxy architecture. It has client-side and server-side connections, both, and they're separate.
It also has an AVR feature: application, visibility, and recording. It's good for customers looking for what is actually happening in their network and where the latency is.
it has TCP LAN and WAN optimization features. It has has caching.
You can create multiple virtual servers on F5 BIG-IP technology, and within multiple virtual servers you can have multiple nodes, where a node equals two application servers.View full review »
It can determine if the system is going down, then route the traffic somewhere else.View full review »
We're able to do load balancing and global load balancing. When you marry those two products together, you can do a lot more. We're able to deliver our applications more securely and faster. It has improved our deliverability where we have more service across the shared data centers. We can intelligently reach all of those client connections across all of the servers and do it fairly quickly. It has helped improve our application delivery and performance.View full review »
It is very intuitive, easy to deploy, and manage.
Users can see a remarkable performance difference from a qualitative sense.
Our experience has been very good, in terms of performance, and securing our application infrastructure.View full review »
F5 BIG-IP is used with good applications and functions as an application firewall with additional features. We will not use any feature or any service unless there is a business case and there is a need for implementation.View full review »
Load balancing generally brings high availability and a bigger ability to scale out. In some cases, it brings security, depending on how it is configured.View full review »
The Local Traffic Manager (LTM) provides a simple low balance and SSL decryption, in addition to some TCP parameters, for incoming and outgoing traffic to redirect appropriate traffic patterns to appropriate servers.
We are using Application Security Manager (ASM) as a web application firewall, where there is a security signature to avoid a web level breach.View full review »
It helps us recognize sessions from certain IPs that are authorized to manage the application. This is a function we haven't found anywhere else.
The most helpful thing is that it's open-source. It's very easy to program and customize.View full review »
The detail that you have available when setting up iRules.
Where we are finding the AWS version helpful is when we are trying to scale up new environments. AWS Marketplace helps here a lot.View full review »
F5 BIG-IP Cons
I used GitHub for autoscaling CloudFormation, and I found two bugs and I submitted them. Their implementation in GitHub could be cleaner and allow for a bit more customization.View full review »
The one gap I saw was that pure LBN integration is a little tricky. The insertion of F5 in LBN is a little tricky. They need to work on something, on products by which they can insert F5 in any sort of cloud environment.View full review »
They could improve the product's ease of use. There is some confusion how to operate it.View full review »
I would like to see improvement in the manageability and easier setup.View full review »
Implementing whitepapers with a lot more applications could easily be added.
There is a challenge in Pakistan. This is when there is a hardware failure. Sometimes, it takes more time to get a replacement because it is sent out from the U.S. or some other regional outpost. Thus, it takes two to three days to receive a replacement.View full review »
There are issues with F5 BIG-IP but they are minor issues not affecting production and services. Sometimes the operations and the facility systems fail. However, there is an alert action from the windows. An ordeal for the manager.View full review »
I would like them to expand load balancing, being able to go across multiple regions to on-premise and into the cloud. This could use improvement, as it is sometimes a little cumbersome.View full review »
I would like to see F-5 implement a regular routing like in other Linux-based devices. When we try and integrate in some complex networks, we have to use some additional routing scenarios from a Layer 3 perspective, then we have some problems. It would be great if this were fixed somehow.View full review »
Logging is a bit of a problem. Logging and monitoring are only in plain text. You have to search and you have to know what you are searching for to find anything. So of course, monitoring and getting alerts for abnormal situations is hard. There are no tools for monitoring and alertsView full review »
For integration with other AWS environments, we do some tie-ins with some autoscaling groups. This has been challenging for us. We have had issues, where when autoscaling groups scale up, there are some instances which are not showing up in the proper size. Then, those IPs would get registered with F5, but never get released. Therefore, we are ending up with a whole bunch of ghosted IPs.
The management interface is unclear, complex, and not concise. I would like a better user interface.View full review »