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.

For the e-commerce domain, many images are present and we require images to be in the best optimized manner to get optimized performance of the application. Additionally, protecting against bot rules, bot and miscellaneous IP for that, IP restriction.

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.

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.

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.

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.

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

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.

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

• CDN configurations are managed using VCL (Varnish Language), and you can do exactly what you want, including modifying the VCL code directly or using the GUI. This is really powerful.
• The CDN performance is really good, and it is fast, all around the world.
• Fastly uses configuration versioning, where you can deploy a new version in less than one minute. This includes a new origin server, caching rules, etc., and you can also rollback in less than one minute.
• The self-service model contains everything, and there is no need to ask for operations to be performed by technical support.
• Fastly CLI is really usefull to modify configuration in a quick way, more user friendly than the API but enought powerful to do what you want, I really like this possibility to make bulk changes