Share your experience using CacheFly

Our main use case for F5 Distributed Cloud Services is the application traffic management and security for our web applications. We rely on F5 Distributed Cloud Services primarily for load balancing, WAF capabilities, and routing traffic to applications across our cloud environment.

We use F5 Distributed Cloud Services as we migrate our online application away from the previous gateway and WAF solution. The application traffic can be protected and managed through the F5 Distributed Cloud Services platform. We use F5 Distributed Cloud Services as a front end for the application traffic with logical HTTP load balancer and hostname-based rules directing requests to the appropriate origin pools.

F5 Distributed Cloud Services has positively impacted my organization from the security point of view, as all our applications are in a very stable, safe mode. This is important, especially taking into account all the sensitive customer data which flows through our systems. Security is the number one feature right now. The stronger security we have, the more reliable we are as an organization.

Since using F5 Distributed Cloud Services, from an operational perspective, being able to see the actual request through the load balancer makes change validation much easier.

The best features F5 Distributed Cloud Services offers in my experience are load balancing, traffic routing, and WAF. These are the strongest features for us. Traffic visibility is also very useful, especially when we are validating changes or troubleshooting routing issues.

Traffic visibility has helped our team significantly. For instance, after a routing change, we can look at the actual requests going through the load balancer and can quickly confirm that the traffic is reaching the new route. This is the most practical example of how we use the visibility.

An improvement for F5 Distributed Cloud Services could be in usability. It is very powerful, but it can also be quite complex. When you have many applications and routes, the troubleshooting process is not always straightforward. Making it easier to follow the traffic path and quickly see where something is going wrong would be a great enhancement.

We have been using F5 Distributed Cloud Services for almost three years. We are in an established project starting from January last year. We are actively migrating an online application from an end-of-life application gateway to F5 Distributed Cloud Services.

F5 Distributed Cloud Services is stable in my experience.

The scalability of F5 Distributed Cloud Services is good enough from my perspective. We have not hit any major scalability limitations so far.

The customer support experience for F5 Distributed Cloud Services was quite positive.

Before F5 Distributed Cloud Services, we used a traditional on-premise F5 load balancer, and for our cloud application, we also used Azure Application Gateway and WAF. We moved to F5 Distributed Cloud Services because those solutions were outdated and were not aligned with the new requirements, specifically security requirements.

F5 Distributed Cloud Services is deployed in our organization as a hybrid model right now, as we are still using all possible capabilities.

My advice for others looking into using F5 Distributed Cloud Services is to do your preparation.

Regarding F5 Distributed Cloud Services's AI capabilities, governance and security are obviously major parts of the product. I feel the way F5 Distributed Cloud Services handles AI governance and security is promising. The capabilities look promising. However, we are not widely using the AI-specific features extensively enough. AI governance and security are one of our critical focuses. Governance, data protection, and having a clear control area around how AI is used would be very important before expanding the adoption.

I cannot judge F5 Distributed Cloud Services's AI capabilities thoroughly at this time. Our use of F5 Distributed Cloud Services today is much more focused on traffic management. I would say it is still too early to assess AI output.

I rate F5 Distributed Cloud Services an eight out of ten. The reason for this eight rating is that we must keep a buffer for future improvements. If I would score a ten, that would mean the product is absolutely perfect and ideal. However, we need room for future improvements.

My main use case for F5 Distributed Cloud Services is to associate SSL certificates to some VIPs, and I also check nodes of servers in a VIP and exclude them or include them. I often use some iRules to show a certain page or another in maintenance mode.

The client I am working for requested that an update should be done on their website, so they wanted to show on the front end of the website a certain page, which we call a courtesy page. It showed, 'Sorry for the inconvenience, this page is not available right now. Wait until 10:00 p.m.' Something similar to this. So, I put this iRule with that HTML page inside, waited to substitute the nodes inside of the VIP, and then removed that iRule and got everything online as usual.

I can add something about my use case for SSL certificates. I do not always import them because the company I work for created an automation that whenever a certificate got renewed, it got imported automatically in F5 Distributed Cloud Services. Sometimes this does not work and I go import them manually.

In my opinion, the best features F5 Distributed Cloud Services offers are that the complexity is very low. It is simple to use and gives the opportunity to do whatever I want, basically. It acts as a firewall and as a load balancer. It is pretty important to use if I have a lot of things online, shared online, and published. The simplicity of the use matches the big difference that it does the job. Also, I can access it by SSH, which is pretty interesting.

I pretty much appreciate the interface of F5 Distributed Cloud Services because it allows me to understand what I am doing, where I am going, and it is pretty comfortable to navigate.

I noticed that with F5 Distributed Cloud Services, I can manage network uptime pretty easily, the nodes inside of a VIP, manage all the VIPs, and all the clusters. It is pretty easy, and all the system runs pretty well.

To be honest, I do not have something to suggest as improvements for F5 Distributed Cloud Services. I think it is complete.

I have been using F5 Distributed Cloud Services since March, which is when I started working for Accenture.

F5 Distributed Cloud Services is stable as a rock.

F5 Distributed Cloud Services' scalability is pretty good.

I did not have the opportunity to use F5 Distributed Cloud Services' customer support, as I have to be honest. In my opinion, when I do not have to use the customer support, it means that it works perfectly.

I did not use F5 Distributed Cloud Services for myself, so I use it for a company. In the previous company where I was, they were using a FortiGate, Fortinet solution for the system. They were load balancing this way, and I did not really prefer it much in terms of graphically, and it was a bit complicated to publish something and to get it rounded up. Then I got to watch in a call, in a meeting, another load balancer, but I do not remember the name. It was pretty basic and easy, and it was more something of a WAF, of a Web Application Firewall. I think that F5 Distributed Cloud Services does the work better.

As I mentioned, I did not choose F5 Distributed Cloud Services myself because the company chose that solution. When I came here, it was already working. They were already working with F5 Distributed Cloud Services, so it was not my choice.

I would give F5 Distributed Cloud Services a rating of nine out of ten.

I did not choose a ten for F5 Distributed Cloud Services because I personally know some load balancers, but I do not really know what is on the market as a load balancer on the enterprise level. So, I did not want to give it a ten because I do not really know how other load balancers work at this moment.

I would suggest trying F5 Distributed Cloud Services in a demo before buying it, but it could really help manage all infrastructure on the web point clearly. So, I would suggest it.