The main use case for Fastly is the primary use case of the CDN, the content delivery network, where our primary website caches all the static content in the nearest POPs, which they call Points of Presence. We use it for the web application firewall to control any malicious traffic.

We utilize the real-time visibility and control over cached content. We monitor how much is cached and how much is offloaded to the servers. We do this extensively to understand what content can be cached versus what content should be dynamic, using the real-time stats.

It combines both the CDN side and the Signal Sciences next-generation WAF. Fastly has a WAF which they bought from Signal Sciences, and that's closely integrated with the CDN. We use both products: the Fastly CDN and the Signal Sciences WAF.

The VCL language is a distinguishing feature, and unlike other CDNs, it's a programmatic language with which we can write all the rules and configurations. That's the best part. VCL is a programming language for managing the cache.

Fastly has POPs with huge servers across the world, so it works effectively everywhere except the mainland China region. They don't have a presence in mainland China compared to Akamai. When we have our business running in mainland China, we have to manage that close to the China mainland, such as Hong Kong and other nearby regions.

Another downside of Fastly is that when we wanted to migrate our API domains, it's lacking the WebSocket protocol. They say it's supported, but it's not fully implemented yet. We tried to implement that and faced some issues with the connections because it requires bidirectional communication through WebSockets, unlike HTTPS or HTTP.

We have been working closely with Fastly for two years, having migrated from Akamai to Fastly.

It was a seamless transition for us, and we have three to four websites that we control.

We have SLAs defined because we opted for enterprise support pricing. The SLAs are very good.

That's the only downside I see, and I have experience with Akamai and Fastly. We have also had Cloudflare in the past, but Fastly seems to be more modern compared to the other providers.

It was absolutely easy, and I would rate it between eight and nine because it was seamless for our use case. Some other companies might have a more complex setup, but for ours, it was easy.

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.

What I don't like about Fastly is that they charge a heavy price. The pricing is different per region. If you have a customer who is international and has deployments in different regions, it is very complicated to calculate the pricing because every delivery region has a different price. AWS also has prices per region, which is a mess because, very often, you have customers who don't know how much traffic they have in what region. Offering them a service and competing against someone who knows that it's very hard because the pricing is per region, and that makes it very complicated to find solid pricing for the tool.

There are customers who shift their traffic. One day, they have a lot of traffic in Europe, and then the next day, they have lots of traffic in Latin America, and then there is always a different price sheet.

The tool basically follows the market. The tool tries to offer everything. I would like the tool to have a much stronger integration of the security product on the platform because products like bot manager or WAF used to be not native. You have to buy Fastly and then some sort of cooperation with some other WAF vendors is needed, but that is not what I am looking for currently.

I have been using Fastly for five to six years.

It is a stable solution.

It is a scalable solution.

The number of customers I deal with is much smaller because Fastly itself makes a lot of direct sales. Fastly doesn't have a very strong partner channel. Fastly doesn't look very good with partners. The tool goes directly to the customer, and it is very hard to cooperate with them.

The product's initial setup phase is straightforward. I would say that the setup is more like using Fastly, which is an embedded local firewall application, which is something I don't look into because I don't want to have a SaaS solution. I want to have a dashboard and configure it. I don't want to run virtual machines or look after a network. I don't want to install anything on AWS or anywhere. I haven't used WAF from Fastly so far because it is one of the two hundred WAFs out there. AWS has its own WAF, and it may not be as sophisticated as Fastly. If you need any integration in Fastly, it is probably good if you use one of the products, like Adobe Experience Manager, or if you are a customer of Adobe. You can also be a user of Magento, which is an Adobe product and has Fastly built-in. Fastly tool is part of some products. The customer already gets part of Fastly as it is built into those applications. It is wise for customers to use Fastly within their products and then additionally buy some extra features from Fastly that aren't standard within the product. Fastly is a company that is aiming for a lot of very big customers. Fastly was a supplier for TikTok, but they are not anymore as it is a very competitive market, and it lost the contract.

In our company, we like Fastly technology, and at the same time, we want to be an agnostic solution provider for multi-service edge providers, which is the reason why we offer Akamai and Fastly. As I am involved in Fastly's technology, I can basically tell my customers to look at different solutions. I can recommend a tool, depending on your use case, and which one would be the best for you. If you want Cloudflare or Fastly, we help you integrate it. As a neutral vendor, I don't stick to just one product, and that is my advantage. Fastly's interest is to win every customer they talk to, so it goes very often directly to the customer because its reseller is selling more than one product and not just Fastly exclusively. I know a couple of customers who do direct business with Fastly, but that doesn't involve me.

You need to pay a premium price for the tool.

In terms of security features, Cloudflare came into the security game very late. Cloudflare has a WAF solution, which it sort of purchased, so it is not native to its portfolio. It kind of becomes native now because they integrate it, and you can have the WAF deployed either locally in your network or upon points of presence with Fastly, which is a legit web application firewall.

It is a good solution. It is a very developer-focused tool. Fastly has an easy setup process. It is a solution that is based on Varnish. Varnish is a caching language. Fastly Varnish Configuration Language (VCL) is a programming language that has already been around since the 1980s. Varnish is very native to developers who run Apache servers, which is also the concept of Fastly. We are using the skills of developers who know the configuration of the web servers, and we accelerate traffic using this special programming language. Fastly competes against Varnish itself because it is not a company. Varnish is an open-source product.

The users should be very strong, especially in order to facilitate quickly; everyone should have a strong knowledge of Varnish Configuration Language, which is VCL. If they just need to locally use the solutions and if they don't need worldwide distribution, they can do it via Varnish without Fastly being only used if you are a big corporation and you need to compute in lots of regions, and you don't want to run all the compute by yourself. If you are a big company and you want to have a global footprint in computing, you can deploy your own servers everywhere, like Azure, AWS, or any computing platform, but then you would run into a lot of costs. Fastly offers a platform, but I don't know how many POPs.Fastly is offering to compute functionality on its platform based on how an oil company sells you oil.

Fastly has a big computing platform, and if it is able to run computing on edge, it can also run AI on the edge because AI is nothing but computing in order to accelerate algorithms on edge, which is where you connect to the internet. If your computer is in London, you probably get connected with a British telecom company, and your first connection out of your house or office is to some sort of server related to a British telecom company, and it is what is known as the edge. If your computer comes from AI, media, or video, you are basically close to the British Telecom network, and the experience will be faster as you won't be able to connect to anything in Zurich, Tokyo, or Moscow. You connect directly to your local provider. Bring computing to the edge so you can accelerate your experience, so it will accelerate AI, video, and anything else because it is closer to you. If you make a request in ChatGPT, the request goes to some server, and that is at the speed of light. If you are connected to a server in Australia, that could take up to 200 milliseconds, which is, like, two-tenths of a second, and if you do that quite often and if the request goes, like, 20 to 30 times, you end up waiting maybe three to four seconds for the answer of your request. If the British telecom, it has gone half a second because it is closer.

I rate the tool an eight out of ten.

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.

Its VCL is very powerful, and the fact that we can interface with a deployed pipeline for the configuration as code is really great. So we don't have to do things with their web interface. Everything can be done programmatically as opposed to by hand.

Fastly is very stable, reliable, and fast. And when Fastly does its technology upgrades, it does a good job.

Stronger analytics would be helpful like showing configurations that haven't served a certain amount of traffic in a while. With many properties, things can get lost track of - duplicates or unused configurations not properly decommissioned.

It doesn't show the number of properties where a configuration change happened within a specific timeframe, or there's some options. There's a lot in that area where things could be improved.

I have been using it for six years.

We never faced any crashes, downtimes, or lagging. Fastly manages its infrastructure really well.

Fastly is very scalable. We haven't had any issues. Our on-prem one, which was one of the concerns, is we, again, can only scale to what you installed as hardware, and we did have some issues a few times with the maximum capacity that it could handle.

So, in our case, it was connections to origin, when we did have a problem.

Support is good; the product works as advertised. We have a Slack connection with them. So we can basically ask for help, live, engage, and ring when they respond. Very quickly.

From the acknowledgment point of view, sometimes it takes a little while to get it to the right place. But a lot of time, just for the nature of the types of things we're asking for, we generally don't ask for Trivial support.

So a lot of the times when we ask for something, it's not hitting tier one or tier two anyway because it's inappropriate for them. So, a lot of times, when we ask something, it ends up needing to be escalated regardless because it'll be of a significant technical nature.

So sometimes you take a little while to get to it. But it's not that it would be unexpected; I have to wait to get it sent to the proper owner.

Moreover, the responses and they answer their questions with good answers, and they don't, like, we don't get that typical BS right around where they just ask us stupid question questions that could make us wait.

They're gonna put that clear up in and ask relevant questions, and they're actually really good.

The GUI is easy enough if you're a small company; the initial setup would be fine. It took us a little while to get our deploy pipeline the way we wanted it to be automatic so that individuals don't have to do the configuration. It comes along with our application deployment.

So, if we're small, it's fine. The GUI is adequate and intuitive enough, and then as you grow and expand and evolve, you obviously wanna go towards using their API to deliver your configuration changes.

In our case, we deployed both on the prem version as well as the cloud. At one time, we did an on-prem version. We got rid of it because the value proposition wasn't there for the cost. We've now gone completely with their hosted infrastructure. Like, we don't do anything on-prem anymore.

We were like, we were very few companies that did the on-prem. But it was last year; we got rid of it because it wasn't something we needed to continue with.

The deployment process was a while back. It was fine. Fastly was very good at what it did.

Deploying something like that is nontrivial because you gotta coordinate hardware installs and circuits when things like that.

We have a good team for the deployment process. We had three or four people on that team that were on that project.

The pricing has been very competitive.

I would recommend reading up on the core functionality of the product and then mapping that to your business use case. And, particularly, cache keys are things you wanna look at. Your cache keys are well thought out so that you don't have something too specific, and you also don't want something too general.

We've had that problem in the past where our cache keys aren't specific enough or are too general, so we go to clear cache, and we're clearing more things than we should.

Overall, I would rate the solution a nine out of ten because I like this 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.

Fastly's UI is reliable. We can use coding with Terraform to configure it with ease.

Fastly's customer service area needs improvement. They should respond faster. They take time to organize internal team meetings after we raise the ticket.

We have been using Fastly for three years.

I rate Fastly's stability a nine out of ten.

I rate Fastly's scalability an eight out of ten.

The technical support services need improvement. We encounter issues while communicating with them regarding different time zones.

The initial setup process is straightforward.

Fastly is less expensive than Akamai.

I rate Fastly an eight out of ten. I advise others to go for Cloudflare if their application is hosted on AWS. They should evaluate Akamai as well. They must decide which product to choose based on price and 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.

Compute@Edge features are valuable to me. The product allows us to overcome architecture on the origin. It enables us to run a pilot very quickly. It also allows us to do A/B testing at scale.

The product should provide improved bot detection and management. The product should also provide support for code management. Everybody working in CDN is currently looking for ways to better manage code deployment with various authorization levels and synchronization with our lower environments. Matching up what's happening in CDN with what's happening on the origin regarding testing would always be useful.

I have been using the solution for three years.

The product is very stable. We had a very stable experience and reliable performance figures with Compute@Edge.

It has been very easy to scale the solution. We're significant users now with the product. They've scaled up with us very easily. Largely, this is because their platform is easy to operate, but also because the support we've had from the product has been exceptional. We call them, and they will ensure that they're giving us the capacity we need to scale up. In my organization, 15 people use the solution. The product is present in multiple countries and multiple locations. Fastly has 60 global points of presence.

Something really good about Fastly is the level of support that they offer, which is exceptional. They have active Slack channels and give you a lot of support from their team to onboard. I was very impressed with that.

We also use Akamai and Cloudflare. We often run dual CDN. We have expertise across all CDN platforms, including CloudFront. We have to understand all the available CDNs. We have to work in lots of those environments, but we do really like the development Fastly has made in Compute@Edge and the stability and performance of their platform. The big advantages of Fastly are the level of support, Compute@Edge functionality, innovation, and cost.

The deployment is fairly simple. The product is deployed in the cloud. We can have a point of presence near us, but we don't use that at the moment.

We deployed our own solution internally within a day. We found it to be very easy. We received a lot of support. Our EdgeOps engineers, front-end engineers and security team deployed the product. The tool does require maintenance. Our CDN or Edge team works within the environment to handle and manage the good bot and bad bot traffic. They also manage the configuration and run Compute@Edge scripts and applications.

We have definitely seen a return on investment. The important thing is that we’re able to use the platform to meet marketing demand and requests from other teams around the business. We're already increasing the return on investment by using the platform more widely across the business to meet our goals.

I've generally found Fastly to be very competitive in pricing, especially around Compute@Edge.

Fasty is very open to running pilots and trials and is very engaged with working with our team to set up their platform. They're a very good consideration not only to run as your primary CDN but also as a dual CDN. They are very open to conversation around it. It obviously improves resiliency and redundancy in our CDN setup. The solution allows you to take advantage of the features that Fastly may have over other CDN vendors within the same architecture. Overall, I rate the product an eight out of ten.

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.

Support is not that great.

I have been using the solution for two years.

The solution is stable. It is still being used in our company.

The product is scalable. More than 100 people, including the network, infra, and WAF teams, are using the solution in our organization.

The initial setup is easy. The end-to-end implementation is quite good. The solution is deployed on the cloud. Support for end-to-end implementation is pretty much good.

The solution is cheaper than other products in the market. The pricing is reasonable.

Fastly acquired Signal Sciences. It is a good product, and it fulfills our requirements. Even if a feature is missing, we can request it, and Fastly will help us. Overall, I rate the tool an eight out of ten.