What is your primary use case for F5 BIG-IP?

The primary use case includes load balancing to serve application servers and basic web application firewall solutions. Our customers use it for that purpose.

I use the solution for load balancing.

I used LTM to segment traffic between servers, secure them from deficient connections, and protect them from web attacks and malicious behavior.

We are using the solution for our internal and client purposes. We are a cloud service provider.

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.

We use F5 BIG-IP Local Traffic Manager to balance traffic.

We use the solution for its load balancing and web application firewall features.

F5 BIG-IP Local Traffic Manager (LTM) has EC, WAF, firewall, network firewall, and CGNAT in one platform.

BIG-IP has multiple uses, including VPN, application firewall, and load balancing.

I used F5 BIG-IP LTM for the backend load balancing for the servers.

I mainly use LTM to protect applications.

The solution is used for deploying applications.

We are using F5 BIG-IP LTM for our application which is a reverse proxy. We use it for availability, and to process the application because it is used in the financial industry.

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.

F5 BIG-IP LTM is used for delivering applications and protecting the application from web attacks.

In the last two years, the F5 BIG-IP Local Traffic Manager implementations for a client had pointers, primarily ones pointing inwards to the onsite cloud-type systems, but they also did have pointers to some cloud-service-based instances as well. So it was actually doing a bit of hybrid.

BIG-IP LTM is mainly used to load balance applications.

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

We use it for server management and application traffic, that is, to load balance between traffic for applications coming from their service. Users coming in are then able to have their traffic go to the service that has the suitable resources or adequate resources.

It is for internal load balancing of servers.

We use F5 BIG-IP Local Traffic Manager (LTM) for the web application firewall and a load balancing system. We are using it in a government project.

I am using F5 BIG-IP Local Traffic Manager for load balancing. For example, I create the virtual server, and in there we have a pool and member server. This is used for simple load balancing. We are using the on-premise and cloud versions of the solution.

We use F5 BIG-IP Local Traffic Manager for our applications. We have six applications and 16 servers currently. We make all our applications and utilize this tool. Some applications are published on LSM.

My primary use cases of this solution are as a big IP solution, a WAF solution, EPM, and reverse proxy.

We are using it for internal traffic management and traffic load balancing. Its version is up to date.

We use F5 BIG-IP Local Traffic Manager (LTM) as a load balancing solution. We use many of the features associated with the solution, such as the Local Traffic Manager and Access Analytics that are associated with the SSL.

In terms of our primary use cases - all our web services, our main web portals, and our TV service sit behind the F5, so any customer would have to traverse our F5 for the services at the back of it. It serves our backend and front end services.

We primarily use the solution for security purposes.

The product can be used for many applications including load balancing and GLB's overload balancing. It depends on the module. If there's a public APM you can use it for WAF and many other use-cases.

I am not the F5 administrator so I don't use all of the features. I primarily perform daily operations such as checking statistics and deploying new virtual servers.

We are using it for web application firewall and load balancing features. We have its latest version.

Mostly I support my clients in relation to the product.

We use the solution as a proxy to our websites, load balancing all our servers as clients come onto our website and use our services. Our website provides around 15 different services. We are customers of F5 and I'm a solutions architect for telecom and network infrastructure.

We are a reseller of F5, but we haven't had many projects that we've deployed with F5. In terms of use cases, it is used when clients have web servers, and they are hosting on their own infrastructure. When they have web applications that are publicly visible, they use F5 to balance that incoming traffic for their web servers.

The solution is mostly used for the LTM load balancer. Recently more of our customers are using it for the web application firewall. Some of my other customers are using the GTM model also.

We are a solution provider and we work with a lot of products from F5. In our internal network, we use F5 BIG-IP. We also have a few implementations with this product, including some that are integrated with other solutions such as IBM Guardium. One of the great use cases is capturing an application user through F5 and then pushing it to Guardium. This is very useful for our customers because they can then connect to the database with a real application user, which is something that is very hard to achieve through other vendors.

We are using this solution as a load balancer and reverse proxy.

Our engineers use various products from the F5 BIG-IP range when creating application solutions. Primarily, we make use of F5 BIG-IP's ASM (Application Security Manager) and WAF (Web Application Firewall). For most of our applications, we require that our servers, and server-related software, are hosted in virtual machine environments.

We are in the security business, basically working in two segments; the first is in the financial sector, with the largest banks in the country, and second, we work with some government organizations and corporate businesses. Only B2B for now, not much retail. We have a few projects in insurance companies. The solution is deployed on-premise in our office and we basically use it for demo and testing purposes. We deploy for our customers both on-premise and on cloud. We are a distribution channel, like a reseller. I'm a channel development manager.

The F5 is something we purchased for another project that has not been turned on just yet.

Our company is based in different geographical locations and we need to create SD-WANs with tight security while allowing remote access to our resources. To manage that and to manage the whole network, we use BIG-IP.

We are using this solution for the web application firewall and load balancing.

Our primary use case for this solution is as an alternative for ADT. We work with standard enterprise customers because this product is not affordable for the SME, it's not a cheap solution. We are partners with F5 and I'm a pre-sales and technical executive.

We are a solution provider and this is one of the products that we implement for our clients. Some of our clients use it as a load balancer. It can also be used as a web application firewall to protect your web-based applications from attacks.

We mainly use this solution for application delivery and application security - the product is used on a daily basis. We are partners of F5 and I'm the head of IT infrastructure.

We use the whole pallet of the Big-IP products starting with the Application Security Management, the web application firewall for the F5. We use it for the protection of files at sites and we also use the load balancer. I also have experience with the airlock and we're now researching the possibility of exchanging our Big-IP system with something else. We're hoping to find a solution that's better for the cloud but which can be a hybrid. We have a partnership with several vendors and I work as an IT security engineer.

Our primary use case is for ADC (Application Delivery Controller) and SSL VPN prospectively worked for the PoC.

F5 has performed marvelously. It certainly holds in value and holds its name.

We use F5 BIG-IP with LTM burst, SM burst, and ETM burst. We use it in our cloud service and all our service centers. We even offer F5 BIG-IP to our partners.

We are primarily using it for load balancing, and with BIG-IQ managing Layer 7 security policies.

We use it to deliver services on the cloud.

We use it for brokering services.

We use it as a load balancer.

We are using it for load balancing and security. When someone requests data through the load balancer, we pull the certificate name out to identify who that person is. This is one of the things that F5 does. We haven't able to replicate this so far with the Amazon products. That is why we are going to F5.

* Load balancing * Certificate management * Pooling of services

We use it for local traffic management and for the application firewall. We are trying to deploy virtual appliances in AWS.

We use it for load balancing and routing.

We use it for a number of solutions that we build, mostly for identity and access management control.

We use it for low balancing. It has been in our environment for four to five years, but I have only been using it for a little over a year.

We use it primarily for WAF.

When we migrate workloads into the cloud, we need the same functionality in the cloud, and low balancing is part of that. Being able to manage the platform on cloud, the same as on-premise, is the use case.

We use F5 for the load balancing of our equipment. We use it for DDoS functionalities in our security solution.

In Vietnam, F5 provides better services.

Primary use case is as our main protection. You can use it for brute force and other kinds of cross-site attacks.

F5 delivers a full range of solutions that simplify service providers’ security architectures while mitigating threats. The full proxy architecture of F5 solutions also allows service providers to attain extensive visibility and control throughout layers 4 through 7. This enables granular control of all connections, more extensive security functionality, and comprehensive end-to-end protection against DDoS and other attacks. F5 solutions protect targeted network elements, the DNS infrastructure, devices, and applications with features that include application health monitoring, a robust web application firewall, web access controls, TCP optimization, web acceleration, L7 DDoS protection, and broad SSL support, including SSL inspection and offload.

We have around 12 data centers. On average, in every data center, we have 14 to 15 F5 load balancers. We manage everything from a central location, then we deploy policy for use, giving us a place for our control managers.

We use it as an LTM and as a reverse proxy to publish web services.

There is more than one use case. The most important is the Local Traffic Manager (LTM). We are using it to load balance our web applications, SSL decryption and application adjusting, along with some TCP features. We are also load balancing traffic between appropriate back-ends for risk.

GTM and LTM are the primary uses of the solution. Our company has two active data centers and a data center that is being activated. F5 BIG-IP helps us a lot.

Publishing of many applications through the F5 reverse proxy to the Internet. We are also using the F5 as an IdP server.

We are using it primarily for load balancing. We also make great use of SSL interception (offloading and onloading), packet inspection, rewriting, and DNS wide IP.

This is for remote access to an internal network of the organization to do all types of work. The requirement for VPN is secure with high performance.

We’re a systems integration company. We propose this solution mostly to our banking customers and large enterprise clients, so that they can load-balance their core banking applications and their main applications. It also provides proxying, the client cannot directly access the server. BIG-IP is a proxy between the user and the server, so the client cannot make connections directly to servers. They land on F5 BIG-IP and then F5 creates connections on servers on behalf of clients. We use the solution for smarter, safer, and reliable connectivity.

The primary use cases are application load balancing and as a web application firewall.