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 WSO2 ESB is an awesome product for companies looking to venture into the world of SOA with an ESB. They have a lot of other products too that can work really well with their carbon infrastructure. The interface is simple for deploying and managing proxy services. You can also write custom modules within the ESB using Java with IDE like Eclipse
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 One of the basic requirement of an ESB product is that it should be able to support transformation. WSO2 ESB provides support of XSLT, so you can transform your request to whatever format. Moreover, transformations like converting your xml payload into JSON and JSON payload to XML are out of the box available. WSO2 ESB provides a scheduler feature, by which you can configure your own scheduler to call a proxy service at a particular time of day or or initiate sequence. WSO2 ESB provides excellent error handling techniques, WSO2 ESB provides detailed error handling scenarios to tackle all the situations. WSO2 ESB also provides custom error handling by which you can make your own custom error message before sending it back to client. 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 While it's easy to configure for a quick start, it is not so easy to deploy by yourself in a complex production scenario. Not very stable for production usage, we encountered several trivial bugs that make us believe that this product is still not widely adopted. Lack of a built in mechanism for auto-restart in case of an application server crash. Read full review Usability Compared to competitors the overall experience has been fine
Read full review Reliability and Availability Lack of auto-restart built-in capabilities. In case of running out of memory there are no built-in methods to recover from a crash, just for example, Oracle WebLogic Node Manager.
Read full review Performance The product is performing well and consuming few resources
Read full review Support Rating Our experience with the WSO2 support has beent satisfactory
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.
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.
Read full review It's the only one truly open source and free.
Read full review Scalability Adding a server node is really straightforward, there are just few point in the configuration files.
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 Very well documented tutorials and case studies makes it easy to learn. It has a really supportive community It is fast and it can easily handle 300 tps of average use on a VM with 4Gig RAM Read full review ScreenShots