CloudFoundry vs. Tanzu Application Catalog

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

The best way to take advantage of VMware Application Catalog (Bitnami) is as in the case I mentioned, that you constantly implement these free software, where any time saved is important in terms of installation, configuration and testing environment, it really is a very useful solution, also if you need a good community and support; however the cloud and VMs solutions is not designed for huge products, these can be slow or remain insufficient if the use of these grows a lot, even though it is an easy-to-use product, you need to have enough knowledge in terms of installation and management of cloud solutions, a beginner can find himself in trouble

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

• pre-packaged templates they provide.
• ease of cloud-deployment of your projects.
• The development community page always has useful information and there is a lot of support.

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

• Possibility to configure the implementation through mobile devices
• Sometimes the performance of the VMs is slower than expected
• A best way to do the upgrades, you have reinstall and reconfigure in this process

Incentivized

Most of it is intuitive. I think some of the awkwardness is found by new users who are unfamiliar with other software applications.

Incentivized

They have an expert team, not just a frontline team that has learned the FAQs but a team that knows the product.

Incentivized

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

VMware Application Catalog (Bitnami) offers better tools to complete the task faster and more efficiently. The customer support and knowledge base is also well presented and trained

Incentivized

• 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

• We save a lot of time implementing the apps, less engineers working on this phase
• The upgrade process of the apps can be a pain and a waste valuable time
• The mains options of the VMware Application Catalog (Bitnami) are free so is important for save money in our organization

Incentivized