Likelihood to Recommend
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. Read full review
It would be a good solution for running serverless applications. Because infrastructure setup and maintenance expenses can be avoided, the investment will pay for itself. The time to value is short, allowing IT to respond to business demands quickly. It aided us in customizing security as well as operating a personal project using to autoscale up and down approach. Also, because there isn't much hassle, items can be pushed into production as soon as possible. Simply push a container, create an application, and you're ready to go. But, It is less suited when you have a static machine or need to keep data in some way and do not want to utilize network storage or a database.
Read full review Pros 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 Managed Environment for partners and customers - shifting skills and speed to CSP A variety of programming model support Elastic scalability for cloud native development and speed Flexible consumption model Containerized workloads with horizontal scalability Here is an example - live demo walk-thru delivered to partners and community: https://www.youtube.com/watch?v=MCBClYgpDFg Read full review Cons 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 For Bigger projects, the Number of jobs and apps can be increased along with maximum memory consumption. The Documentation can be more extensive for freshers and get more engagements from the newcomers. Moving around the security changes can be tricky and hard to change. Read full review Usability
IBM Cloud Code Engine is good for developers to create a microservice based on typescript and nodejs. The tool can help mange the project very well. It decrease the difficulty for developement and increase deloping speed. However, the code engine UI on IBM cloud does not contain enough features it can support.
Read full review Alternatives Considered
While Docker shines in providing support for volumes and stateful instances, Cloud foundry shines in providing support for deploying stateless services.
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.
Read full review
What impresses me most about IBM Cloud Code Engine is the container workload management capability and the Cloud services and dataflow monitoring functionalities. Data security and network security control via IBM Cloud Code Engine is quite excellent and very responsive data integration functions and the first deployment is not very technical.
Read full review Return on Investment 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 IBM Cloud Code Engine secures my underlying infrastructure and help manage multiple project data. Easy resources management and the multiple transactions tracking through IBM Cloud Code Engine is amazing. Effective Application isolation from other workload using IBM Cloud Code Engine is perfect. Read full review ScreenShots IBM Cloud Code Engine Screenshots