Azure App Service vs. IBM Cloud Foundry

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Azure App Service
Score 8.8 out of 10
N/A
The Microsoft Azure App Service is a PaaS that enables users to build, deploy, and scale web apps and APIs, a fully managed service with built-in infrastructure maintenance, security patching, and scaling. Includes Azure Web Apps, Azure Mobile Apps, Azure API Apps, allowing developers to use popular frameworks including .NET, .NET Core, Java, Node.js, Python, PHP, and Ruby.
$9.49
per month
IBM Cloud Foundry
Score 6.0 out of 10
N/A
IBM Cloud Foundry is an IBM version of the open-source platform designed for building, testing, deploying, and scaling applications. Enterprises can run Cloud Foundry in a public isolated environment, while natively integrating with other IBM Cloud services, such as AI, Blockchain, and IoT.
$0.07
Per GBH
Pricing
Azure App ServiceIBM Cloud Foundry
Editions & Modules
Shared Environment for dev/test
$9.49
per month
Basic Dedicated environment for dev/test
$54.75
per month
Standard Run production workloads
$73
per month
Premium Enhanced performance and scale
$146
per month
Community Runtimes
$0.07
Per GBH
Offerings
Pricing Offerings
Azure App ServiceIBM Cloud Foundry
Free Trial
YesYes
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional DetailsFree 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.
More Pricing Information
Community Pulse
Azure App ServiceIBM Cloud Foundry
Considered Both Products
Azure App Service
Chose Azure App Service
AppServices that's easier to manage than its competitors, specially if you have everything in Azure. But also that's the most expensive service when you escalate or start using it for massive data processing. It would be an excellent containers platform if were easier to deal …
Chose Azure App Service
Azure is some what easy to use and we can learn the azure platform easily. And mainly for students they are giving free credits. So by using the credits we can learn or deploy using that credit
Chose Azure App Service
In terms of deploying your apps, Azure App Service provides a solid foundation. You may use either the Azure command-line interface or the Web Portal to administer these apps. As a whole, I find You may easily deploy your apps to Azure App Service to be a really difficult …
Chose Azure App Service
We didn't use other App services because we use Azure as our cloud provider and our first experience was with Azure App Service
Chose Azure App Service
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 …
Chose Azure App Service
  1. We selected Azure over Linode because of the CI/CD integration with DevOps.
  2. Azure has integration with docker containers.
  3. Azure has intehration with Sprint Planning.
Chose Azure App Service
Azure App Service will give you a very solid and strong platform to deploy your applications. It gives you great interfaces to manage those applications either through a Web Portal or the Azure command-line interface. However, I consider Azure overall to be very complex and …
IBM Cloud Foundry
Chose IBM Cloud Foundry
IBM Cloud Foundry is our first choice industry-standard platform as a service (PaaS) which has always provided us with quicker, simpler, and more consistent ways for the deployment of the cloud-native applications which in result saved us lots of time and money.
Chose IBM Cloud Foundry
IBM Cloud Foundry is easier and faster to get going and offers the same benefits we needed.
Chose IBM Cloud Foundry
Dynatrace Network Application Monitoring (NAM), formerly DCRUM, Azure Application Gateway and Azure App Service
Chose IBM Cloud Foundry
When I started with prototyping five months ago, I tried IBM Cloud Foundry and AWS, but finally I preferred IBM Cloud Foundry.

I selected IBM Cloud Foundry because IBM service CLI is quite simple to use in devops. It works with the recent versions of Python and it's not …
Chose IBM Cloud Foundry
Why I prefer IBM Cloud Foundry platform over AWS Elastic Beanstalk or Heroku Platform is the automation of development process and pushing of projects to cloud with clear step by step instructions - which is available on the documentation. I can say categorically, the terminal …
Chose IBM Cloud Foundry
IBM Cloud Foundry is easy to use and allows for fast and easy deployment of web apps.
Chose IBM Cloud Foundry
IBM Cloud Foundry provides many programming languages. It is a managed service and it allows us to use only the resouces without the managed overhead.
Chose IBM Cloud Foundry
Ease of use and all the capabilities we need are well built-in. Though we had to work around for p2p security and log draining which is not bad.
Chose IBM Cloud Foundry
Cloud Foundry has lot of benefits because platform as a service provided for the developers to implement applications based on the use cases. Different use cases required different buildpacks to run on. It has flexibility to code, push, and run flexibility. Provided ease of use …
Chose IBM Cloud Foundry
We have had to move our deployments to Kubernetes because we needed more reliability. We moved to Google because IBM rates and billing was so backward and expensive. Our client was also very angry at all the outages, lost revenue, production down time and inordinately expensive …
Chose IBM Cloud Foundry
IBM Cloud Foundry is among the services provided by our cloud provider. This is why we choose to go with Cloud Foundry.
Chose IBM Cloud Foundry
While we are still looking at kubernetes and other services, we will continue to use Cloud Foundry because of the advantages it provides. The support from IBM is good and take a lot of work that our developers and ops had to do away.
Chose IBM Cloud Foundry
AWS and Digital Ocean; Access to a larger pool of services; whatever your business needs, IBM provides it.
Chose IBM Cloud Foundry
It is a cloud-based solution and for all my customers that want to migrate to cloud, this is the solution that we are proposing to customers, as it provides a lot of benefits over private cloud. Scalability and resiliency are not a major challenge and it can be used with other …
Chose IBM Cloud Foundry
CF is what we initially went with to establish a development pipeline and start our cloud journey, now we are expanding this and although we are now pulling in many other tools and functions around CF, it is not being replaced. It stands out as having a key place working ‘with’ …
Chose IBM Cloud Foundry
IBM Cloud Foundry (CF) is simpler and there is a service model that fits most of our internal services. We are going to Loopback for API and Node.js and we have an easy path to go with Bluemix. It's a very easy way to start if you are moving to the cloud and mainly if you are …
Chose IBM Cloud Foundry
We chose to go with more bare metal options since Bluemix didn't really offer these at the time. It was simpler to get up and running with the bare metal service, and we felt that any problems we ran into would be a result of our own incompetence rather than problems with the …
Chose IBM Cloud Foundry
I have use EC2 and Microsoft's Azure. To me, both Azure and Bluemix were fantastic, but they each had some pros and cons. Azure had more services to offer, but their biggest flaw was in their inability to integrate and work with external platforms, APIs, Programs, etc.. Like …
Chose IBM Cloud Foundry
While IBM works well is when being used by large organizations, these other vendors work well with smaller organizations. We ended up being willing to pay more for Heroku, as they have such an easy-to-use service, and our deployments worked as expected every time.
Chose IBM Cloud Foundry
Used AWS and Azure.
AWS has more features and a far superior interface responsivesness. It's actually usable! That being said default configurations and menus in AWS are more cryptic then necessary.
Azure seems to be the gold standard for pre-configuration and ease of use. …
Chose IBM Cloud Foundry
Bluemix had a much easier route to get into the artificial intelligence side of things with Watson skills. It also seemed a lot more straightforward to use things like the Weather Channel data, sentiment analysis... etc., than the others. I'd also had a bad experience with AWS …
Chose IBM Cloud Foundry
Not even close--as noted in previous answers, we will likely use the competition before even considering IBM Bluemix.
Chose IBM Cloud Foundry
We have used Red Hat which does not do business in Australia with people like us. They were a promising service (PaaS) while we were able to use the free version but as soon as we needed access to serious mobile-first services we had to pay and their policy meant we had to …
Chose IBM Cloud Foundry
I like when the provider offers cloud deployment via standard orchestration mechanisms (like Docker, Kubernetes, DCOS) This is currently well covered by Azure. Amazon also has good flexibility (supports Kubernetes, DCOS). It's good that Bluemix added support for Docker and …
Features
Azure App ServiceIBM Cloud Foundry
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
Azure App Service
8.0
Ratings
0% above category average
IBM Cloud Foundry
7.6
Ratings
5% below category average
Ease of building user interfaces10.00 Ratings7.00 Ratings
Scalability10.00 Ratings8.50 Ratings
Platform management overhead4.10 Ratings8.50 Ratings
Workflow engine capability5.00 Ratings8.00 Ratings
Platform access control10.00 Ratings10.00 Ratings
Services-enabled integration10.00 Ratings7.50 Ratings
Development environment creation10.00 Ratings7.70 Ratings
Development environment replication10.00 Ratings6.40 Ratings
Issue monitoring and notification8.00 Ratings4.70 Ratings
Issue recovery6.00 Ratings7.50 Ratings
Upgrades and platform fixes5.10 Ratings7.50 Ratings
Best Alternatives
Azure App ServiceIBM Cloud Foundry
Small Businesses
AWS Lambda
AWS Lambda
Score 8.7 out of 10
AWS Lambda
AWS Lambda
Score 8.7 out of 10
Medium-sized Companies
Red Hat OpenShift
Red Hat OpenShift
Score 9.3 out of 10
Red Hat OpenShift
Red Hat OpenShift
Score 9.3 out of 10
Enterprises
Red Hat OpenShift
Red Hat OpenShift
Score 9.3 out of 10
Red Hat OpenShift
Red Hat OpenShift
Score 9.3 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Azure App ServiceIBM Cloud Foundry
Likelihood to Recommend
7.9
(0 ratings)
8.5
(0 ratings)
Likelihood to Renew
-
(0 ratings)
7.0
(0 ratings)
Support Rating
10.0
(0 ratings)
-
(0 ratings)
User Testimonials
Azure App ServiceIBM Cloud Foundry
Likelihood to Recommend
Azure App Service is well suited in our case :
  • Our website is developed by our tech partner in a full Microsoft Azure cloud based environment.
  • We gave them specific access rights and the CI / CD integration helped a lot for updates and improvements deployment.
  • Most of the infra issues we had with our website weren't coming from App Service
Read full review
IBM Cloud Foundry is a solid service from the IBM Cloud platform. It is easy to learn, and does not usually require you to make drastic changes to your existing applications. It is especially good for new applications that are cloud native, or micro-services, that can be easily updated and deployed. With its blue/green deployment, you can achieve 0 downtime for your customers.
Read full review
Pros
  • Super quick & easy to deploy new apps in visual studio
  • Easy scaling to help reduce costs during off-hours
  • The powerful Azure ecosystem offers a lot of functionality that ties in well with Azure App Service
Read full review
  • Intuitive user interface makes it easy for anyone to use, regardless of their professional background.
  • A lot of the services integrate well with external platforms, APIs, and programs, not just IBM services. A lot of the competitors in this space lack this ability.
  • Maybe it is just our contract in particular, but support and help is always made available.
Read full review
Cons
  • Abstraction of computing resources like Heroku does with dynos.
  • Azure Portal overall is pretty bloated and that affects managing Azure App Service applications.
Read full review
  • Sometimes the API Connect GUIs don't cleanly disengage after attaching models or updating schema and it is hard to know what has been written successfully and which (if any) models or tables were missed. I shouldn't have to manually check through a list of 377 models to find the ones in and out of a list on either models, folder or database tables. Printing a summary even in logs which did a "diff" sort of thing between 'task-set' and 'task-completed' (referring to attaching models or updating schema as tasks here as 'tasks').
  • Provide access to Postgres Database in Sydney datacentre for Australia.
  • Clearer documentation around setting up a secure (referring to SSL and certificate setup here) server on eg, chubby1.au-sydney.mybluemix.net.
  • Allow a ramp in pricing onto the Blockchains. We will not be able to afford it until quite a few years into production, even if we launch successfully.
Read full review
Usability
I enjoy the fact that Azure App Service can be managed by the Azure portal and a fully graphical user interface, as well as from two different flavors of command-line interface, i.e. Azure CLI and Azure Powershell. By utilizing the Azure Cloud Shell, we are able to switch between Azure Bash (CLI) and Powershell at any given moment and manage the Azure App Service settings from devices of any form-factor (Web based management).
Read full review
No answers on this topic
Support Rating
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
No answers on this topic
Alternatives Considered
In terms of deploying your apps, Azure App Service provides a solid foundation. You may use either the Azure command-line interface or the Web Portal to administer these apps. As a whole, I find You may easily deploy your apps to Azure App Service to be a really difficult platform for novices to get their feet wet. First and foremost, I'd look at Heroku's user interface and the way it abstracts compute units.
Read full review
IBM Cloud Foundry is our first choice industry-standard platform as a service (PaaS) which has always provided us with quicker, simpler, and more consistent ways for the deployment of the cloud-native applications which in result saved us lots of time and money.
Read full review
Return on Investment
  • Download time is reduced because of auto scaling feature.
  • Insight tool helps in finding issues quickly.
  • CI/CD has helped in automation.
Read full review
  • This was the founding solution used to allow us to move in to and test out a cloud pipeline. This is what paved the way for a full production cloud solution to be possible.
  • Having Cloud Foundry at the base of our development and sandpit environment, segregated away from our standard on premise solution has moved away red tape and ensured an agile way forward.
Read full review
ScreenShots