Amazon CloudFront vs. StackPath Edge Delivery

Amazon CloudFront is best suited when there is a need of speed in serving static and dynanic web contents of a web application. If the content is already in that edge location, CloudFront delivers it immediately. If the content is not currently in that edge location, CloudFront retrieves it from an Amazon S3 bucket or an HTTP server. Amazon CloudFront is not appropriate in case users can tolerate some delays or servers are present near to the location of user. It also Integrates through the W3 Total Cache plugin. Amazon CloudFront Pricing based on bandwidth usage that's the best part of it.

Incentivized

It is great as a primary or backup CDN. We have had no issues with performance. The cache hit ratio is high. Some of the options are hidden within the API and you have to configure them with API calls, such as configuring signed fetch requests to an S3 origin. These should be in CLI or Web Console. The deployment of edge side scripts with the CLI or CI/CD could be improved.

Incentivized

• Solid CDN services, does what it says on the tin
• Lots of configuration options, which allow for different setups and pricing strategies
• Lambda@Edge integration allows for really quite complex behaviours to be executed in the cloud at the edge node itself. This means there are a huge amount of possibilities for shaping and altering traffic close to the viewer.
• Simple integration to other AWS services (e.g. S3)

Incentivized

• Price competitive.
• Easy to use.
• Good reporting.
• Quick to deploy.
• Start-up friendly.
• Good technical information via blog, FAQ and community discussion.
• I can talk to real person for urgent support.

Incentivized

• If price is the main concern, CloudFront is not the cheapest-in-class by a wide margin
• Some of the settings are not obvious to new users, and the management dashboards could use work
• Lacks fine-grained access controls and statistical reports for usage

Incentivized

• Analytics.
• Many options hidden in API.
• Web console.

Incentivized

Easy way to integrate a CDN within the AWS infrastructure. It allows further customization based on company needs.

Incentivized

CloudFront is a good CDN solution. It can be a bit complicated to implement depending on your needs, but AWS tech support is great. You get to avoid a ton of upfront costs by going with CloudFront. It works best in conjunction with other AWS services in your infrastructure. Once you set it up, you won't need to do much to maintain it. It just works.

Incentivized

Have used the IBM Cloud Content Delivery Network for a very short time span like a couple of weeks. Both the setup as well as interactions with other services are a little complicated or not straightforward when compared to AWS. Also, IBM cloud has less number of edge locations than AWS Cloudfront.

Incentivized

1. Total solution (CDN, WAF, monitoring, DNS hosting) which offers me a turn-key solution.
2. Power customer portal which empowers to configure my service performance.
3. Clear and granular service packages that meet my budget.
4. They provide in-person real-time communications which can provide me urgent support.
5. They offer start-up friendly program.

Incentivized

• RoI for using CloudFront is immense. You can use it for all your certificate management and static asset management of your websites using CloudFront.
• It is as good or better than any other CDN provider with multi-region support across the world using AWS regions.

Incentivized

• Easy 25-30% improvement in website performance vs non CDN solution
• Less expensive and faster object storage than AWS
• Aided greatly in maintaining KPIs in terms of performance, availability

Incentivized