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
Oracle Java Cloud is especially appropriate for moderate to complex Java applications. Due to BYOL licensing, it is also works well when you are planning to do dev and test in-house and then deploy it on Oracle Java Cloud. It is not well suited for simple Java applications due to the cost of Oracle Java Cloud. Simple applications don't need the fully managed aspect of Oracle Java Cloud.
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 Configuring and then deploying Java applications is straightforward and can be done very easily. Management console for Oracle Java Cloud is integrated with the rest of the IT stack, making it easy to figure out performance bottlenecks in Java applications and Java PaaS. 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 Pricing can certainly be improved as the cost adds up for dev/test environments using the Oracle Java Cloud platform. It is hard to customize Oracle Java Cloud for complex Java applications requiring high bandwidth memory and network requirements. 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 Google App Engine
is great for Java applications where you are using other Google components already, for example Google GCP, Google BigQuery, etc. Redhat,
, and Pivotal CloudFounder are great when the application is very complex and includes components that are Java and non-Java based (Python, etc). Amazon AWS is more difficult to configure than Oracle Java Cloud - Oracle Java Cloud has simpler UI.
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 Positive impact on ROI by reducing the time to deploy Java applications in the cloud. Positive impact on business objectives by reducing the CapEx needed to hire staff to deploy and then later maintain the Java instances. Read full review ScreenShots