Amazon CloudFront vs. Incapsula

Parked in front of an nginx instance that serves all of our static assets. Performance and reliability have been excellent, and the header pass-through rules are wonderful. Price is affordable, as well.

CDN

media CDN and edge cache, poor mans reverse proxy to separate static asset traffic from application traffic from marketing traffic etc

Used by Yotta for performance acceleration.

CDN for out website and purely JavaScript web apps.

For those sites that have crazy mad spikes in traffic.

We chose CloudFront mostly because it’s incredibly popular. But also because it’s the recommended CDN for Heroku, which means there shouldn’t be any problems using them together. Rails makes it really easy to drop in a CDN reference for your app so that when your assets get compiled, they’re shipped off to the CDN and then deployed with your app.

So anytime we push to Heroku, we’re pushing up to CloudFront (if the assets don’t already exist). One major issue we still haven’t been able to solve involves Fonts. Has anyone actually been able to get fonts served up through CloudFront using Rails 4 and Heroku? Literally spent hours researching this and can’t find any solutions. We ended up just referencing a CDN for all the font libraries.

We have a separate distribution for each environment, since I don’t think it’s possible to use the same distribution for the multiple domains.

We leverage Cloudfront to deliver our product to our customers users around the world

Just awesome service from amazon to deploy your app around the world. International deployment used to be impossible for start-ups, it is now available and affordable.

CloudFront's easy to use in front of S3, especially for videos, which don't load reliably from S3. We've noticed latency issues with CloudFront, and so don't use it for everything, though.

CloudFront 는 수십 테라 바이트의 이미지 트래픽을 안정적으로 소화해 주며, CFRC 약정을 통해 요금 할인 혜택도 추가적으로 얻을 수 있습니다.

All images, CSS, and JS route through CloudFront edge servers.

Cloud Infrastructure

RTMP Streaming.

Amazon CloudFront is used for serving media assets securely

Our interface is beautiful and serves up a lot of static content. CloudFront helps us deliver the content quickly.

Service of image assets

Handle DNS requests and easily change the AWS service it directs to without fiddling with DNS

Cloudfront keeps the load of distributing our assets off our single Amazon S3 bucket. It also allows for configuring SSL for our custom domain.

basic

I use CloudFront for lightning-fast worldwide distribution, caching and HTTP redirects.

This is our CDN for game assets.

Audit the CloudFront configurations for best practices and standards.

Public-facing image store.

비디오 스트리밍 및 CDN

Cache and serve images.

Fine CDN, integrates well with other AWS services

Distributing worldwide and fast!

Easy to connect to S3 for static content distribution, specially images

CDN for Vaultize public cloud.

In my opinion, the best Content Delivery Network for the money. This, along with other services from AWS's ecosystem make this the easy choice for CDN. Fast, simple and cheap.

It gives me TLS that I don’t have to manage, for free.

Serves the entire front-end.

Region-specific image caching and content-delivery to speed up page loads and increase responsiveness.

We use Cloudfront for our website.

CloudFront is our CDN - it allows our website to be retrieved quickly and viewed all around the world.

We use this because it's a CDN that sits in front of our static resources hosted in S3. It makes it so that users in other countries can have quick access to our portal.

The logical choice for an AWS hosted web site to optimise bandwidth at edge delivery locations.

Fast CDN with vastly distributed edges.

Edge locations.

Distribute large data sets and installers for desktop apps

PrometheanTV uses the Amazon Cloudfront CDN for a variety of networking delivery reasons including caching, SSL termination, and various content delivery needs.

We use Incapsula for DDoS protection and traffic scrubbing.