Amazon CloudFront vs. IBM Cloud Internet Services

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

In terms of business challenges, it simplifies the job of my engineers and significantly increases the productivity of my teams when they collaborate with IBM teams all over the world. Now that we have completed a proof-of-concept using the services supplied by IBM, we expect it to assist us in managing them more efficiently; thus far, management has been straightforward.

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

• build servers in Power PC architecture (ppc)
• take advantage of IBM datacenters infrastructure around the world
• continue to use your apps running on AIX

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

• Request proxying is done by way of DNS name resolution, which is inflexible.
• Proxy services do not work on wildcard DNS entries.

Incentivized

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

Incentivized

I have seen faster and more user friendly interfaces like Azure

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

I have used Salesforce to explore it as an app but I have found them both able to solve my needs and requirements when it comes to security. While I choose IBM Cloud Internet Services for more accessibility, a better price was available with Saleforce. Although that is just my observation.

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

• Reduced security configuration time for Internet of Things applications by more than 50%
• Provided better security incident SLA for CouchDB databases via IBM Cloudant
• Reduced security verification time for CloudFoundry applications by ~15%

Incentivized