CloudFoundry vs Microsoft Azure

• 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

• Perhaps the biggest advantage of Microsoft Azure is its ease of integration with other Microsoft products. If you're used to using Excel, Access, SQL Server, and other Microsoft products, Azure will fit in nicely.
• Azure does a good job at pointing the user into user-friendly methods for data capture and analysis. In fact, I think Azure does the best job at this compared to competing tools.
• Microsoft Azure has recently made strides in implementing advanced analytics, such as machine learning. Their advances are great and integrate nicely with the tool.

Read full review

• 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

• Sometimes its a bit overwhelming as to the volume of functions
• The layout could be more intuitive
• While there are a lot of support docs it could be laid out a bit better to help you get where you need to go

Read full review

• 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

• This solution has allowed reduction of hardware costs. Virtualization is by far much less expensive than onsite platforms.
• Buying and configuring systems is costly in terms of initial investment and specialized staff. Azure minimizes those costs.
• Azure has created a positive impact on our business objectives in the sense that it has allowed system integrations to become available in a quicker time frame than typically expected.

Read full review