Share your experience using CacheFly

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.

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.

I believe that Fastly should provide guidelines for their WAF blocking rules. It should be public what the rules are that are blocking their contents.

I believe Fastly should provide regional IP addresses instead of POP IPs.

Fastly should provide features similar to Cloudflare regarding a block list. Additionally, a POP address should be there with a wide range of IP addresses provided, public static IP addresses, so customers can integrate egress IPs.

Fastly should provide WebP image processing on the backend instead of on the fly. It would be a very useful feature to avoid unnecessary time for browser to browser and local cookies.

I believe that Fastly service has a few gaps. We are not getting quick responses from Fastly technical support engineers. Sometimes they depend on their D3 developers. There should be transparency.

I have been using the solution for around six to seven years.

I believe that Fastly service has a few gaps. We are not getting quick responses from Fastly technical support engineers. Sometimes they depend on their D3 developers. There should be transparency.

Neutral

We offer two kinds of teams. We have predefined Fastly for Adobe Commerce Cloud and on-premises merchant, and multiple times we use Cloudflare.

We use Cloudflare for cost considerations for some customers.

My name is Parth Pandya and my job title is Technical Support Engineer at Adobe.

Fastly provides CDN, WAF, image optimization, and IP restriction.

I am a technical person, not working in sales, so I don't have specific metrics.

Overall, Fastly is good for performance, good for CDN, good for WAF, and average for services.

We are partners in Adobe Commerce Cloud.

I have rated Fastly 9 out of 10.

I have experience with Cloudflare; I use them all the time, including WAF and DNS.

I'm using Cloudflare on all my domains, and any client domains I have, I set them up with a Cloudflare account.

I've been using Cloudflare DNS product since they came out; that's basically the main use of what they offer.

The best features for Cloudflare WAF are being able to control access and being able to control your security by adding that extra layer above and beyond our internal firewall. I assess the impact of Cloudflare WAF's integration with existing web technologies on my performance and security measures as being basically a front end for edge computing. All the DNS and everything is routed through Cloudflare, so anybody coming to any of the sites has to go through Cloudflare first. They are basically the first wall of defense.

The WAF's advanced reporting and analytics tools add a layer that we're able to visualize and see before it actually hits the local firewall.

For Cloudflare DNS part, I also use it as a DDoS, CSPM, or CDN; I use all the features because it hits them before it hits us. The best features of Cloudflare DNS are the tunneling and the ease of use to create new records, just being able to manage any domains that you own and then have them take care of it. They send you a bill, and it's the only way to go.

Cloudflare makes it easier for me to handle and set up DNS for multiple users and multiple clients, and basically go in and access their account, make the changes they need, and it's a one-stop shop.

I don't know what areas could be improved with Cloudflare WAF; Cloudflare is constantly improving and adding features to their feature set. They're doing a good job, and as far as DNS and support for any domains that I create or my clients create, it's mandatory for me to make sure that they have Cloudflare as their DNS provider.

The Cloudflare load balancing capability hasn't really helped in enhancing my website's uptime and resiliency because we don't really get that much traffic; it's mostly remote users, and web hosting is done by a web hosting service. It doesn't pay to try to host your own website.

I'm using Cloudflare on all my domains, and any client domains I have, I set them up with a Cloudflare account.

I assess the performance of the DNS services in terms of speed and reliability for my organization and my clients as being fine; I don't see any speed loss. Most of the encrypted DNS we put through our servers ends up at Cloudflare anyhow.

I would rate the technical support with Cloudflare as excellent every time I've had to call them; I haven't called them but three times.

Their support, regardless of whatever the problem may be, is great every time I've had to call them; I've only had to call them three times in four years.

Positive

The initial setup with Cloudflare is pretty straightforward for me; I've done enough of them.

It's also straightforward for someone new, but if you understand networking and DNS tunneling, knowing DNS is a must, but other than that, it's great.

In terms of return on investment with Cloudflare, it costs my time to set them up, but basically once they're set up, it's done, and if they're on a free plan or even if they're on a pay plan, they aren't doing that kind of volume that they really have to worry about any pricing issues.

I haven't evaluated other options such as other WAF solutions as a front end; I've used other DNS providers before, but as soon as I found out about Cloudflare, I switched all my stuff and my clients over and haven't switched back. It's a lot more valuable than what they charge.

The main differences between Cloudflare and one of the others I used, such as DynDNS, are that once they got bought out by Oracle, they turned to crap; Cloudflare allows you to set up a free account and still have DNS capabilities on the fly, and if you have to make changes, it's simple.

I have dealt with Cloudflare Web Application Firewall since they had it out.

I have a lot of clients that are basically individual businesses and non-profits, lawyers, doctors, and various other professionals.

It integrates with my existing or my client's existing systems.

I have no idea if there's anything specific that might be nice to have coming in the next releases; I don't keep up on it. Basically, when I go and set up a site or look at any of my sites, I discover they came up with something new and check it out.

My experience with the pricing or the licensing of the product is that a lot of the stuff you can do for free, so the pricing is definitely fair. A lot of my clients don't need that much of what they have to offer, and what they have to offer on free plans is generally enough, so it doesn't cost them anything.

With the WAF feature, I haven't paid that much attention to what Cloudflare is doing regarding addressing security threats such as SQL injection and cross-site scripting, but we have firewalls on all of our systems and intrusion detection that are on site.

I would rate Cloudflare DNS overall as a 10 out of 10. There's definitely a little room for improvement as they could be 10 out of 10 at some point, but they're close to 10 out of 10 now.