Share your experience using CacheFly

F5 Distributed Cloud Services provides secure, consistent application delivery and protection across multi-sites and edge environments, such as Azure or on-premise. In our environment, we use F5 Distributed Cloud Services to secure and connect workloads during hybrid deployment. For example, we had customer-facing APIs split between Azure and on-premise, and instead of building complex VPN tunnels, we relied on multi-cloud networking to establish security connectivity. At the same time, the WAAP service protects those APIs from bot traffic and injection attacks.

F5 Distributed Cloud Services helped us unify security and performance across distributed environments. For example, when I rolled out a new customer portal, traffic was split between on-premise and servers in the cloud. F5 Distributed Cloud Services' global load balancing kept performance consistent worldwide, while WAAP blocked malicious bot traffic that spiked during launch week. The combination meant we could scale quickly without compromising security.

F5 Distributed Cloud Services' best features are those that unify security, networking, and visibility across multi-cloud, multi-sites, and edge environments. They stand out because they reduce complexities while keeping applications resilient and secure. F5 Distributed Cloud Services' global load balancing route with traffic intelligence across regions ensures performance and uptime for customer-facing applications.

Day-to-day, the networking and visibility features of F5 Distributed Cloud Services make operations easier because they remove complexity and provide real-time insight into what is happening across multiple environments. Multi-cloud networking lets us securely connect workloads across Azure and on-premise without building or maintaining complicated VPN tunnels.

F5 Distributed Cloud Services has had a very positive impact on our organization by strengthening security, simplifying networking, and improving visibility across multi-cloud environments.

F5 Distributed Cloud Services could be improved to make daily operations smoother and more powerful. For example, simplifying onboarding would be beneficial; when I initially set up across multiple clouds, it felt complex. A streamlined wizard or automated connection would reduce deployment time.

I have been using F5 Distributed Cloud Services for around three years.

F5 Distributed Cloud Services are stable.

F5 Distributed Cloud Services are very scalable because they are a service.

The customer support is great and very fast.

I evaluated other options before choosing F5 Distributed Cloud Services, including Azure WAAP.

F5 Distributed Cloud Services' AI governance and security are designed to make automation trustworthy, compliant, and resilient against threats. For example, the policy enforcement AI applies compliance rules consistently across workloads, embedding governance into daily operations.

AI outputs from F5 Distributed Cloud Services are considered highly accurate and reliable, particularly in anomaly detection, WAAP, and compliance reporting. Independent testing has shown a near-perfect score in detecting OWASP Top 10 risks and bot attacks, which validates its reliability in real-world environments. I would rate this product a ten out of ten.

My primary use case for Fastly is using it as a CDN to speed up my customers' access to the applications.

A specific example of how Fastly has helped improve my customers' access to the application is that it caches static content and makes it more quickly accessible to users. Additionally, internally it allows me to evolve through code and not go through configuration with many clicks as I had to do with other alternative products. Here it allows me to integrate it directly into the code.

I consider the best features that Fastly offers to be cost and the ability to have it integrated into the code development flow.

I have noticed a significant difference in cost compared to other similar solutions.

Fastly has a wide number of configuration features that can be performed, and I emphasize that they can be done from code, which makes it much more traceable.

Fastly has positively impacted my organization by helping to obtain better solutions in less time and in a much more traceable way. A specific example that reflects that impact is that we have improvements in traceability by having the changes integrated into the Git repositories and having the possibility of doing a rollback in the event of any problem in a very simple way.

I think Fastly could improve by improving the documentation and having some code examples so that it is easier for developers, since at the beginning it becomes a bit complicated.

I have been using Fastly for a year and a half.

I consider Fastly to be stable.

I rate the scalability of Fastly as very good.

I would describe Fastly's customer support as fast and efficient when I have had to use it. I rate customer support on a scale from 1 to 10 as eight.

I used CloudFront before Fastly, and I decided to switch because of this product's greater capabilities and lower costs.

I have seen a return on investment, particularly in time savings, especially regarding the changes.

In terms of price, I find it good, and as I mentioned, the implementation cost had some difficulty at the beginning due to the learning curve.

My advice to others who are considering using Fastly is that they evaluate it and not always think of using the native CDN of the cloud they work in. I rate this review as a seven out of ten.