Azure Cloud Services vs. CloudFoundry

Microsoft Azure Cloud services is a good choice for hosting web applications, based on requirements it can be simple websites or complex web services as well as it provides automating application development and deployment pipeline. It's less appropriate in case of cost-effective option for organizations with tight budget constraints. For very basic static websites, Microsoft Azure's offerings might be seen as overkill.

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

• Effective service management and performance monitoring capability.
• Reliable security management with excellent access controls.
• Best orchestration and easy configuration management.
• Easy on compatibility testing and change management.

• 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

• Latency and bandwidth as we often see gap here
• There were many challenges as a developer while migrating our DB from on prem to cloud
• System downtime is also one issue that can be improved

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

As a certificate developer and consultant, I love using Azure, it's interface is developer friendly with well guidance and support. Also there are a lot of service for any work, Azure ecosystem is sufficient to complete your all developments needs. So based on that I feel Azure is good and gives better developer experience.

Incentivized

I feel AWS offers a robust and versatile platform for cloud infrastructure and services. It's scalability, reliability array of tools make it a top choice for businesses of all sizes. AWS has better open source communities such as Linux, Jenkins and GitHub in comparison to Azure service cloud

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

• Azure's services and automation capabilities contribute to operational efficiency.
• Azure's scalability ensures optimal performance during peak demand periods and cost savings during off-peak times

• 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