CloudFoundry vs. Microsoft Azure

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.

Incentivized

Actually, migrating to Microsoft Azure is a good solution for almost any situation, especially when all components of your network are ready to become cloud-based. The only drawback I personally encounter frequently is that older software packages cannot always be easily picked up and moved to Microsoft Azure in an optimal manner.

Incentivized

• 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

Incentivized

• Azure simply provides end to end life cycle. Starting from the development to automated deployment, you will find [a] bunch of options. Custom hook-points allow [integration] on-premise resources as well.
• Excellent documentation around all the services make it really easy for any novice. Overall support by [the] community and Azure Technical team is exceptional.
• BOT Services, Computer Vision services, ML frameworks provide excellent results as compare to similar services provided by other giants in the same space.
• Azure data services provide excellent support to ingest data from different sources, ETL, and consumption of data for BI purpose.

Incentivized

• 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.

Incentivized

• In our experience, Azure Kubernetes Survice was difficult to set up, which is why we used Kubernetes on top of VMs.
• Azure REST API is a bit difficult to use, which made it difficult for us to automate our interactions with Azure.
• Azure's Web UI does a good job of showing metrics on individual VMs, but it would be great if there was a way to show certain metrics from multiple VMs on one dashboard. For example, hard drive usage on our database VMs.

Incentivized

We have been very satisfied with Windows Azure and now a lot of our business depends on it as more teams are now deploying their applications into Azure. Our next step is to have our Infrastructure team move their resources to Azure. It will take awhile for that to happen but we are positive that it will.

Incentivized

Microsoft Azure's overall usability has been better than expected. Often times vendors promise the world, only to leave you with a run-down town. Not the case with our experience. From an implementation perspective, all went perfect, and from the user-facing experience we have had no technical issues, just some learning curve issues that are more about "why" than "how"

Incentivized

It has proven to be unreliable in our production environment and services become unavailable without proper notification to system administrators

Incentivized

Support is easy with all the knowledge base articles available for free on the web. Plus, if you have a preferred status you can leverage their concierge support to get rapid response. Sometimes they’ll bounce you around a lot to get you to the right person, but they are quite responsive (especially when you are paying for the service). Many of the older Microsoft skills are also transferable from old-school on-prem to Azure-based virtual interfaces.

Incentivized

As I have mentioned before the issue with my Oracle Mismatch Version issues that have put a delay on moving one of my platforms will justify my 7 rating.

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.

Incentivized

I feel that Microsoft Azure typically outperforms Google Cloud Platform in hybrid cloud capabilities, integration aspects, and, primarily, security compliance features. Azure offered superior integration with Microsoft's enterprise software ecosystem, and it's second to none in my opinion. This made it the natural choice for most, especially if heavily invested in Windows, Office 365, or Active Directory deployments. We chose Azure over GCP because we simply needed Windows workload support as a strong driver, more access to global regions, and let's not forget that most tech teams in an organization are Microsoft Certified, which makes skillset transfer from on-prem to cloud a minimal learning curve over shifting to a different provider.

• 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.

Incentivized

• Times and growth went into it. By balancing on-premises maintenance with continuous cloud improvements, we’ve budgeted and planned endlessly increased capacity.
• In today’s world of cyber-crime, clients can put even more faith in what they’ve heard. We built an innovative single-sign-on hub for all users. Also, other business platforms use Azure application gateways, reducing worker switching time and increasing productivity.
• Its step can automate to improve the investment. In addition, we can integrate our organization’s credentials into an authorization for other systems.