Cloud Foundry vs Heroku comparison

"My favorite component of IBM's solution is Node-RED, which greatly shortens the amount of time required to develop, test, and deploy new applications."

"IBM is the only vendor to offer integration with blockchain for smart contract development."

"Cloud Foundry builds the runtime environment directly without requiring dependency management from the user."

"We use Heroku to run generic data. We also use it for our customer development environment. It helps us to build and test websites."

"It is easy to deploy applications, and we don't need to bother about software updates on the server. We don't need to bother about machines, servers, and hardware. We only need to care about the system and functionality that we need or want to develop. They take care of everything else. It provides high availability. It is a pretty good solution that provides everything that we need. It has everything that we need to run our applications. We have many different applications, and we generate three million bills for a company in Brazil. We see more than a billion requests per day in another application. Everything works just fine, and it is very good."

"The most valuable feature of Heroku is the continuous integration and applications it provides."

"The platform is very Node.js-friendly, which is something that is important to us."

"One of the best things about Heroku is that it is very easy and straightforward to deploy an application."

"What I found most valuable about this solution is that it's easy to use and integrate with GitHub actions."

"Valuable for us was the fast deployment. This means the time to market is improved without pain for developers."

"It's easy to push a change and to deploy new things."

"In IBM Cloud, the product has been deprecated in favor of Kubernetes, which is a more complicated infrastructure to manage."

"After the initial excitement period with Node-RED is over, you crave the need of additional integrations to third-party services."

"We have to do daily restarts of some processes, which is annoying, and the support for custom CI could be better."

"The tool's configuration is complex."

"Heroku had an authentication problem a few months ago, but they solved it."

"They could flesh out some of their analytics a little more."

"I improved the application performance by monitoring and adjusting the cleaner configuration to help set better lightweight limits on containers that run the app instances."

"Heroku should increase its slug size limits."

"We don't find the pipelines intuitive. The user experience could be better. Having to set up multiple apps, then a pipeline, seems like an overkill on the amount of work to do."

"I think this solution would be improved if free demos were available indefinitely."

"You are allocated a minimum amount of resources in the free tier. This seems fair and highly scalable, as you pay per usage as per cloud pricing schemes."

"The pricing models should be reworked to the needs of a wider range of companies. Some customers will not be able to afford it until quite a few years into production, even after good PoC results and a successful launch."

"IBM has a free tier and payment option depending on the products selected."

"Its price is very good."

"The price of Heroku could be less expensive."

"The tool is free."

"There is a standard fee for a processing unit, they call them "dynos," and then you pay for add-ons."

"I rate the tool's pricing a three out of ten."