I am using Fastly in the Adobe Commerce Cloud project. In this project, it is working as a reverse proxy for CDN and WAF, web application firewall, additionally image optimization.

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.

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

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.

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

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

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.

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

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.