Amazon CloudFront vs. Edgio 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

Limelight's tech support and their attitude are tremendous. They are always available, willing to assist and quick. They are problem solvers with a can-do attitude.

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

• We used Limelight Networks (LLNW) for content storage and reporting. They continued to update and improve the platform. Their customer communication approach had evolved over the years to become very good.
• We webcast live events throughout North America and abroad from multiple locations for multiple clients, simultaneously.
• We built applications on top of LLNW infrastructure.

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

• We found the LLNW business model and therefore workflow is not set up for multiple live webcasts. It can be done but it is not cost-effective as compared to competitors.
• While their contracts evolve to be more competitive, those original customers/supporters are trapped in old un-competitive contracts and sales blames the lawyers for their inability to make changes.

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

We have moved our live webcasting and archived hosting away from LLNW. There were some technical hurdles that we could not overcome, even with their technical support. For our business model, LLNW's fee structure was not competitive with others in their space.

We do appreciate them for trying though.

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

• We built our live and archived webcasting part of our business around the LLNW platform. We built a successful business with the assistance of their tools and network. Management is really working hard to ensure clients are happy and are being assisted by the organization.

Incentivized