What is our primary use case?
Fastly serves as an Edge Cloud platform and CDN that we use for real-time Edge Caching and instant caching purging, allowing us to update data globally within seconds. It sits between our enterprise users and backend servers, caching content, specifically candidate data, so we do not need to load that data every time.
Fastly's caching and purging significantly improve our application performance and security by caching and delivering content from Edge locations closer to users, optimizing performance for our high traffic web app by caching static assets like candidate data and API responses at the Edge locations. When we call an API from the backend while requesting a page with candidate data, we initially store it in the Edge location after the first call, and subsequent calls use the cached content, blocking malicious traffic and filtering requests before they reach our servers.
We also use Fastly for cache purging to instantly update content across all Edge nodes, significantly reducing page load time, backend traffic, and improving the experience for our global users, especially in the European regions.
What is most valuable?
The best feature that Fastly offers is the Edge location, which reduces latency, making our applications work smoother because we do not have to constantly call the backend. Real-time Edge Caching is crucial for us as it enables efficient data retrieval without constant queries, while instant cache purging and powerful Edge computing capabilities instantly update data across all Edge nodes, reflecting changes globally in seconds.
Edge computing is excellent because it runs code closer to the user, utilizing WebAssembly for fast execution, and stands out with microsecond startup time, eliminating the need to hit backend APIs for logic execution. The key point is the secure, fast execution within microseconds.
Fastly positively impacts our organization by enhancing our application's performance through observability and Edge computing capability, as we needed to get data quickly, reducing latency for millions of users in European regions. We observed a 30 to 50% reduction in response time and a significant reduction in backend load of 40 to 60%, improving visibility through a real-time dashboard for monitoring traffic, errors, and performance.
We measure the 50% reduction in response time by checking the P95, where we assess how quickly 95% of APIs respond, after implementing Edge locations and caching data closer to users. Initially, we faced load time issues, but after deploying Fastly and optimizing our queries, we achieved a response time cut to less than 1 millisecond from an initial 3 to 4 seconds. We utilized a tool starting with S, specifically Sentry, to track API response times.
What needs improvement?
Fastly can be improved in certain areas such as VCL, which is powerful but has a steep learning curve for normal users. A more user-friendly, UI-based configuration could simplify the experience, alongside better templates for common use cases and dashboard improvements, as the current dashboard feels complex for beginners, and pricing can be hard to predict for smaller companies.
I chose 8 out of 10 because it has excellent performance and low latency delivery, making it suitable for larger applications, with strong Edge Caching and instant purging capabilities. However, VCL complexity and pricing predictability, especially for smaller companies, along with a user-friendly dashboard are areas impacting my score.
For how long have I used the solution?
I have been currently working in my field for three years.
What do I think about the stability of the solution?
Fastly is quite stable according to my experience, being highly reliable for enterprise-scale applications with high uptime guarantees and strong global infrastructure, though no service can be 100% immune to outages.
What do I think about the scalability of the solution?
Scalability-wise, Fastly proves very scalable, having supported our growth from 10,000 to 1 lakh users, seamlessly handling massive traffic without requiring backend changes due to its globally distributed Edge network and stateless API-driven design.
How are customer service and support?
We have not needed customer support so far, but the 24/7 helpline is excellent for addressing critical issues, demonstrating the team's technical expertise in CDN and Edge architecture.
Which solution did I use previously and why did I switch?
Previously, we used Cloudflare, which provided similar CDN and security features but lacked the Edge computing capabilities we needed. Fastly offers the performance and control we want over caching logic, whereas Cloudflare simplified setups but did not meet our growing performance requirements.
How was the initial setup?
We purchased Fastly through the AWS Marketplace.
What was our ROI?
We see a clear return on investment with Fastly, mainly through improved performance, reduced infrastructure cost, and better user experience, realizing a 30 to 50% reduction in latency and page load time, ensuring users experience a seamless workflow, while reducing infrastructure costs by 40 to 60% because Edge Caching minimizes backend traffic, resulting in lower computing costs.
What's my experience with pricing, setup cost, and licensing?
The pricing of Fastly can be hard to predict because it is primarily usage-based with minimal setup costs and flexible licensing. It operates on a pay-as-you-go structure, but costs scale with traffic, requiring monitoring to avoid unexpected spikes based on data transfers and the number of requests handled. Setup costs are low since no infrastructure needs provisioning, mainly focusing on DNS configurations, cache rules, and origin integration, with customized pricing for our enterprise needs including SLAs and support.
Which other solutions did I evaluate?
Before choosing Fastly, we evaluated Cloudflare, valuing its all-in-one solution for global coverage and security, but as we scaled, we found Fastly better suited our needs for more control over caching logic.
What other advice do I have?
I advise others considering Fastly that if their application plans to grow significantly without increasing backend servers, this structure is very appropriate, making it ideal for startups building applications to enhance bandwidth over the years. I gave this product a rating of 8 out of 10.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner