Fastly Reviews

I use the solution in my company for security, WAF, and CDN media delivery.

We are using Akamai, Cloudflare, and Fastly. In order to be a hybrid reseller, we want to be an agnostic vendor. We have all three in our portfolio, and they offer quite the same solutions, like edge security, security on the edge, and delivery acceleration of websites. There are also zero-trust solutions, like Cloudflare and Akamai. Fastly is not as much of a zero-trust solution. There is no such feature that is special. I am in this market, and I want to be an agnostic reseller, giving advice to my customers in their use cases.

I use the product mostly for its Compute@Edge capabilities. Fastly is a content delivery network with various functions inside CDN. It has a functionality around security. It also has a content delivery functionality, which is a more standard function within CDN. If you are accessing a website locally from Mumbai, and these servers are based in California, you get a more localized version of the content. Content delivery is something that all CDNs do.

As technology has improved, we're able to do far more than just serve content at the CDN level. We're able to manipulate the HTML requests, rewrite those requests, redirect them, and do forward rewrites. We can carry out a lot of functions, run scripts, and even store data. It is an area that Fastly is very active in.

The solution has increased our velocity significantly. We can carry out pilots and tests far quicker than we used to. We can work out what works for us as a business and then scale it up very quickly. We're able to provide a much faster user experience by using the solution.

We use the solution for CDN, preventing Layer 7, Layer 3, and Layer 4 DDoS attacks, and for Layer 7 web application attacks.

Overall, it is a good product. If we make any changes in one version and it doesn't work or something goes wrong, we can revert to the old version. We will not lose our configuration. For every change, we will have a separate version. We can switch back to the older version if we add anything new that doesn’t work. 

The solution provides good WAF features. Rate limiting is a good feature that protects from volumetric attacks. The product is easy to use and easy to implement. It is quite a mature product.

We use Fastly to track the logs to get the details in case of malware attacks.

The product helps our organization to access sites located in different regions quickly. It makes the sites more reliable.

We use the solution to protect front-end delivery networks. It helps us with caching and firewall purposes.

The solution efficiently works for protecting the network and caching. Also, it has a convenient log management system.

We're using it as the primary content delivery network for a large number of websites that we're responsible for, and we're using it in a configuration of an edge and a shield in front of our organization. 

And we use it in our deployed pipeline. So everything is configuration, is code. We use their VCL technology quite extensively for the functionality of the Edge behavior.

Fastly's instant purging feature improved our content monitoring processes. One of the differences between CloudFront and Fastly is the time to purge. 

So, Fastly's time to purge is very quick. And we've automated it with some front-end API calls. We've even integrated it with Slack so that we can push that clearing of content to a Telstra approach. So the content developer or the person who has the issue with the stale content can actually be empowered to clear their own cache without having to go through someone with the appropriate permissions. So, the fact that we can expose that with API calls is pretty good. 

Moreover, I can see service history and service metrics. So, it's mostly metrics and historical data. For example, how many times do specific properties have the highest rate of, say, 500 errors or something?

Moreover, Fastly helps our company manage a traffic spike during some high-traffic attempts if we have any.

Fastly's request collapsing is their secret sauce, and you get that with Varnish. That's really their massive value proposition, and that they in high traffic spike, even if we have our caching configuration low, it still protects our origin from a big traffic stop because we only get, like, one request coming in. Because that's what they do. They collapse the request such that we might get a thousand people asking for the same piece of data that's not in the cache, but they don't come at us with a thousand requests, the origin. They send one request to the origin and then wait for it to come back, and then they populate the sibling characters with that answer. So it's a sort of table state functionality that they provide that is really key to their value proposition.

I manage CDN configurations for my customers. 

We use this solution to ensure availability and performance for all of the websites we manage. 

We are able to accelerate websites all around the world while they are hosted in a single location.

We are a partner of Fastly and we resell Fastly CDN to our customers. We plan the right configuration for their needs after we learn about their business, and we advise them of which features would be good for them to use. Following this, we do the complete CDN configuration, new release, maintenance, etc.

We can deploy a new configuration very quickly. If our customers express a new need, we are able to give them a working solution in a few days, and sometimes just a few hours later.

We can address all kind of requests, as the VCL let us configure websites in the exact way that we need.

We easily migrated several customers with all of their websites, and they are all happy with this solution.

The statistical data and real-time graphics are very useful to check whether we have chosen the correct settings. Based on the results, we can adapt the settings as needed.