CloudFoundry vs Salesforce Lightning Platform (formerly Salesforce App Cloud)

• 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

• Reports and dashboards - I can build my own reports very easily to see upcoming renewals, first-year clients and so on. Then, I can create my own custom dashboard to track my favorite reports.
• Opportunities and quotes - when I first started here we didn't use Opportunities for tracking renewals and upgrades. Now, it's easy to see what I'm working on and when ready I just add the products to a quote and it sends it to our billing for really fast invoice creation. It used to take me hours to do this and now it's seconds.
• I love using activities - it keeps me organized and up to date on all my accounts that I manage. Plus, I can create future tasks so I don't forget to reach out.
• I can send mass emails to any group of clients and I can create nice email templates with "placeholders" which allow me to use the first name of the main point of contact across hundreds of organizations. Again, this saves me lots of time.

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

• It can be a bit buggy at times, like randomly not letting you save or making you refresh the page or do the same action, and then it will save.
• Bugs really are the main issue here. Otherwise it's great with reporting!

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

• ROI - It allows us to handle billing and see if the client is being charged the correct amount so our books stay balanced.
• Communication - It allows for all of our workers to see the notes of previous representatives so that no one is in the dark when re-engaging.
• A negative would be that it is difficult to merge marketing initiatives, so unless someone uploads the Excel sheet of leads into the system (which is easier said than done) there could be duplications of effort.

Read full review