What users are saying about
8 Ratings
131 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 8.3 out of 100
8 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 8 out of 100

Feature Set Ratings

  • CloudFoundry ranks higher in 1 feature set: Platform-as-a-Service

Platform-as-a-Service

8.7

Azure App Service

87%
9.8

CloudFoundry

98%
Azure App Service ranks higher in 7/11 features

Ease of building user interfaces

8.0
80%
2 Ratings
10.0
100%
1 Rating

Scalability

10.0
100%
2 Ratings
9.0
90%
1 Rating

Platform management overhead

8.5
85%
2 Ratings
N/A
0 Ratings

Workflow engine capability

8.0
80%
1 Rating
N/A
0 Ratings

Platform access control

8.5
85%
2 Ratings
N/A
0 Ratings

Services-enabled integration

9.5
95%
2 Ratings
N/A
0 Ratings

Development environment creation

8.5
85%
2 Ratings
10.0
100%
1 Rating

Development environment replication

10.0
100%
2 Ratings
10.0
100%
1 Rating

Issue monitoring and notification

7.5
75%
2 Ratings
N/A
0 Ratings

Issue recovery

8.5
85%
2 Ratings
10.0
100%
1 Rating

Upgrades and platform fixes

8.5
85%
2 Ratings
10.0
100%
1 Rating

Attribute Ratings

  • CloudFoundry is rated higher in 1 area: Likelihood to Recommend

Likelihood to Recommend

7.8

Azure App Service

78%
6 Ratings
10.0

CloudFoundry

100%
1 Rating

Support Rating

10.0

Azure App Service

100%
4 Ratings

CloudFoundry

N/A
0 Ratings

Likelihood to Recommend

Microsoft

You may easily deploy your apps to Azure App Service if they were written in Visual Studio IDE (typically.NET applications). With a few clicks of the mouse, you may already deploy your application to a remote server using the Visual Studio IDE. As a result of the portal's bulk and complexity, I propose Heroku for less-experienced developers.
Read full review

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.
Read full review

Pros

Microsoft

  • It has options to deploy using CI/CD.
  • It has great integration with Azure Devops
  • It has all the common runtimes, so we don't need to install softwares.
Read full review

CloudFoundry

  • 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
Read full review

Cons

Microsoft

  • the learning curve can be tough (just like other azure services)
  • the UX/UI could be more intuitive (just like other azure services as well)
  • monitoring can be hard to understand
  • Microsoft's learning resources are hard to understand
Read full review

CloudFoundry

  • 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.
Read full review

Pricing Details

Azure App Service

Starting Price

$9.49 per month

Editions & Modules

Azure App Service editions and modules pricing
EditionModules
Shared Environment for dev/test$9.491
Basic Dedicated environment for dev/test$54.752
Standard Run production workloads$733
Premium Enhanced performance and scale$1464

Offerings

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services

Entry-level set up fee?

No setup fee

Additional Details

Free and Shared (preview) plans are ideal for testing applications in a managed Azure environment. Basic, Standard and Premium plans are for production workloads and run on dedicated Virtual Machine instances. Each instance can support multiple applications and domains.

CloudFoundry

Starting Price

Editions & Modules

CloudFoundry editions and modules pricing
EditionModules

Footnotes

    Offerings

    Free Trial
    Free/Freemium Version
    Premium Consulting/Integration Services

    Entry-level set up fee?

    No setup fee

    Additional Details

    Support Rating

    Microsoft

    We had an issue where we deployed too large of a resource and didn't notice until the bill came through. They were very understanding and saw we weren't utilizing the resources so they issued a generous refund in about 4 hours. Very fast, friendly, and understanding support reps from my experience.
    Read full review

    CloudFoundry

    No answers on this topic

    Alternatives Considered

    Microsoft

    Azure has many data center, their services are more reliable. Azure has way more features than both Linode and DigitalOcean. If someone wants a complete reliable service, he/she must go to Azure instead of Linode and DigitalOcean because even though azure charges more, it is worth the money you pay there.
    Read full review

    CloudFoundry

    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.
    Read full review

    Return on Investment

    Microsoft

    • Reduced the deployment time of ASP .NET applications in the company.
    • Gave us an alternative to quickly deploy our applications without granting access to the version control system to a third platform.
    Read full review

    CloudFoundry

    • 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.
    Read full review

    Add comparison