F5 states that the "brain" of the BIG-IP platform, Local Traffic Manager (LTM) intelligently manages network traffic so applications are always fast, available, and secure.
N/A
NGINX Plus
Score 8.6 out of 10
N/A
NGINX Plus is presented as a cloud‑native, easy-to-use reverse proxy, load balancer, and API gateway, from F5.
$849
per month billed annually
Pricing
F5 BIG-IP Local Traffic Manager (LTM)
NGINX Plus
Editions & Modules
No answers on this topic
Team
$849
per month billed annually
Advanced
$2,099
per month billed annually
Enterprise
Tiered Pricing
Offerings
Pricing Offerings
F5 BIG-IP Local Traffic Manager (LTM)
NGINX Plus
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
—
More Pricing Information
Features
F5 BIG-IP Local Traffic Manager (LTM)
NGINX Plus
Application Servers
Comparison of Application Servers features of Product A and Product B
I mean the only reason we changed away from it was price and it just simply had to do with the licensing that Citrix was offering on the NetScalers. They had basically an all you can eat consumption license that we were easily inside of with all of our VDI usage, whereas with F5 we had to buy the hardware and we had to license the software. Any place you need to actually do traffic balancing at scale, it's a fantastic product. I couldn't recommend it highly enough. There's just some things that hardware SSL offload and hardware load balancing just simply can't be equal that I don't know if there's a better product on the market for that.
Makes our life easy as application admins in securing our applications and making them accessible. We can easily add an application within a few minutes and define the backend servers right away.
Sure. It does load balancing fantastically. I mean, it's an industry standard product for that. We also use it for TLS offload for applications. Those are the two main use cases for that. We do also use some of the I rules for traffic filtering. We've used that in some of the external facing services. It does a really nice job with that. It's a little bit complicated sometimes and some of the Cipher Suite stuff is interesting.
Some of the stuff you have to dive into the CLI to really use, I'm going to reach back to the previous employer for this. So I had a much greater degree of involvement with it at that point in time for, I was the crypto guy at the company and I had to design all the cipher suites that we actually implemented on our front end banking products. So in order to do that, I had to dive into it, download all the Cipher suites, figure out the actual order of operation for them, how they were selected because I wanted to design the Cipher Suites to actually provide a specific customer experience for the types of connections that our customers were likely to initiate. Getting at that information was a giant PITA. It was poorly documented at the time. I'm not sure if it's documented any better now. Every time the software changed or got upgraded, made your version, I'd have to do it all over again because the upgrades to the stack, which looked like it was based on open SSL, but it was heavily modified with a different syntax. Oh yay. That's fun too. So I had to write giant documents describing all of the ciphers that I was designing for this because it just kept changing all the time. So I didn't care for that aspect of it. Traffic management does a great job for that.
F5 has always been one of the best products we have in the data center. We had few issues with the BUG and Code upgrades but the main use cases for F5 was always top notch. From High availability to Globally load balancing applications across multiple data centers and muti cloud environments.
I am very comfortable with this product not only configuring it but automating it as well. There are not many configurations or situations where I do not know how to implement it on the device. I find it straightforward and easy to use.
We had an issue after upgrading from RHEL 7 to 8, and there were some issues that the security team imposed upon the platform with a scanning tool. We also had a VXLAN environment that was not properly sending a gratuitous arp to the network. NGINX support was instrumental to speedily resolving our issue.
F5 is doing its specialized function. There is no other product that can beat them. We are extremely happy with the product. Especially on load balancing, traffic redirecting TLS encryption, and SNI modification. We will continue to explore F5's product, especially on the public cloud side. e.g. NGINX.
It has allowed us to let application developers know that the issues are with their application and not due to the network, because of where it sits. This has been invaluable when troubleshooting issues when they arise. Knowing whether or not traffic is even hitting the F5 BIG-IP Local Traffic Manager (LTM), either ingress or outgoing. If the Dev's information is not even making it to the F5 BIG-IP Local Traffic Manager (LTM), we can quickly tell them and let them figure the issue out on their own, saving the rest of the Network Team from getting that 2am call.
We are planning by using NGINX it can greatly reduce our OPEX by 50% "just our own running APIGW" the cascading effects in the long run will be much more.
