What users are saying about
336 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 8.8 out of 101
5 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 9.5 out of 101

Add comparison

Likelihood to Recommend

Amazon Web Services

AWS is a very scalable Platform as a Service (PaaS) -- making it usefull for all sizes. With AWS the failover model can be complicated in terms of selecting the right option for you. Failover within a distribution center is one level, while zone level fail over is a larger one. Be sure to understand your capability needs and discuss with AWS these different choices.
No photo available

CloudFoundry

It's well suited if:
  • The organization has large number of applications that needs to be deployed frequently.
  • The organization is tied to the DevOps mindset.
  • The organization has programs in different languages.
  • The applications does not need EJB's support that servers like web logic provide.
It's less suited if:
  • The applications needs security configuration within the same CloudFoundry instance.
  • The organization, for whatever reason does not want developers to manage the instances.
Anudeep Palanki profile photo

Feature Rating Comparison

Infrastructure-as-a-Service (IaaS)

Amazon Web Services
8.3
CloudFoundry
Service-level Agreement (SLA) uptime
Amazon Web Services
8.9
CloudFoundry
Dynamic scaling
Amazon Web Services
9.1
CloudFoundry
Elastic load balancing
Amazon Web Services
8.7
CloudFoundry
Pre-configured templates
Amazon Web Services
7.6
CloudFoundry
Monitoring tools
Amazon Web Services
7.5
CloudFoundry
Pre-defined machine images
Amazon Web Services
7.9
CloudFoundry
Operating system support
Amazon Web Services
7.9
CloudFoundry
Security controls
Amazon Web Services
8.4
CloudFoundry

Platform-as-a-Service

Amazon Web Services
CloudFoundry
9.8
Ease of building user interfaces
Amazon Web Services
CloudFoundry
10.0
Scalability
Amazon Web Services
CloudFoundry
9.0
Development environment creation
Amazon Web Services
CloudFoundry
10.0
Development environment replication
Amazon Web Services
CloudFoundry
10.0
Issue recovery
Amazon Web Services
CloudFoundry
10.0
Upgrades and platform fixes
Amazon Web Services
CloudFoundry
10.0

Pros

  • Complete Failover and Disaster Recovery services which scale to your desired need
  • Several service level options from dynamic storage pricing to pre-allocated
  • Customer service responsiveness -- issues are resolved with a quick email or phone call rapidly
No photo available
  • Support for Orgs and Spaces that allow for managing users and deployables within a large organization.
  • Easy deployment, deploying code is as simple as executing single line from CLI, thanks to build-packs.
  • Solid and rich CLI, that allows for various operations on the instance.
  • Isolated Virtual Machines called Droplets, that provide clean run time environment for the code. This used to be a problem with Weblogic and other application servers, where multiple applications are run on the same cluster and they share resources.
  • SSH capability for the droplet (isolated VM's are called droplets), that allows for real time viewing of the App code while the application is running.
  • Support for multiple languages, thanks to build-packs.
  • Support for horizontal scaling, scaling an instance horizontally is a breeze.
  • Support for configuring environment variable using the service bindings.
  • Supports memory and disk space limit allocation for individual applications.
  • Supports API's as well as workers (processes without endpoints)
  • Supports blue-green deployment with minimal down time
Anudeep Palanki profile photo

Cons

  • AWS is really difficult to use if you do not have any training.
  • You need to create your own backups. I cannot verify this, but a co-worker of mine stated that he did now create a back, and lost several items.
  • It is very expensive for everyday use. AWS is for people that have done the research, and know exactly what they need. These instances are not toys, believe me.
Michael Timms profile photo
  • Does not support stateful containers and that would be a nice to have.
  • Supports showing logs, but does not persist the logs anywhere. This makes relying on Cloud Foundry's logs very unreliable. The logs have to be persisted using other third party tools like Elk and Kibana.
Anudeep Palanki profile photo

Likelihood to Renew

Amazon Web Services9.4
Based on 10 answers
I would gladly rely on AWS for any large-scale application deployment. For prototyping and small-scale applications, a more heavily managed environment on top of the 'bare metal' virtual infrastructure, such as Heroku or Elastic Bean Stalk, is probably a more productive approach in most cases
No photo available
No score
No answers yet
No answers on this topic

Usability

Amazon Web Services9.0
Based on 3 answers
Easy to use/learning curve. If you are new to the use of cloud storage, AWS is your entry point. If you have experience in that field, AWS is the way to go.
Miguel Angel Merino Vega profile photo
No score
No answers yet
No answers on this topic

Reliability and Availability

Amazon Web Services9.0
Based on 1 answer
Availability is very good, with the exception of occasional spectacular outages.
No photo available
No score
No answers yet
No answers on this topic

Performance

AWS does not provide the raw performance that you can get by building your own custom infrastructure. However, it is often the case that the benefits of specialized, high-performance hardware do not necessarily outweigh the significant extra cost and risk. Performance as perceived by the user is very different from raw throughput.
No photo available
No answers on this topic

Support

Amazon Web Services3.0
Based on 3 answers
Neutral, no experience with either.
No photo available
No score
No answers yet
No answers on this topic

Implementation

Amazon Web Services10.0
Based on 3 answers
The API's were very well documented and was Janova's main point of entry into the services.
Brian Lusenhop profile photo
No score
No answers yet
No answers on this topic

Alternatives Considered

I selected AWS for my development environment and disaster recovery, due to the simplicity compared to other vendors.
Andy Turner profile photo
While Docker shines in providing support for volumes and stateful instances, Cloud foundry shines in providing support for deploying stateless services.Heroku shines in integrating with Git and using commits to git as hooks to trigger deployments right from the command line. But it does not provide on-premise solution that Cloud foundry provides.
Anudeep Palanki profile photo

Return on Investment

  • Dynamic scaling has allowed us to match cost to revenue producing traffic
Jeff Stockamp profile photo
  • Positive impact, since it simplifies the deployment time by a huge margin. Without cloud foundry, deploying a code needs coordination with infrastructure teams, while with cloud foundry, its a simple one line command. This reduces the deployment time from at least few hours to few minutes. Faster deployments promote faster dev cycle iterations.
  • Code maintenance such as upgrading a Node or Java version is as simple as updating the build-pack. Without cloud foundry, using web logic, the specific version only supports a specific version of Java. So updating the version involves upgrading the version of web logic that needs to involve few teams. So without cloud foundry, it takes at least few days, with cloud foundry, its a matter of few mins.
  • Overall, happier Developers and thats harder to quantify.
Anudeep Palanki profile photo

Pricing Details

Amazon Web Services

General
Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No
Additional Pricing Details

CloudFoundry

General
Free Trial
Free/Freemium Version
Yes
Premium Consulting/Integration Services
Entry-level set up fee?
No
Additional Pricing Details