Cloud Foundry vs Heroku comparison

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

"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."

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

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

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

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

"Thanks to Heroku, we don't need to do as much direct management in AWS."

"The product is stable."

"The solution's most valuable feature is the auto maintenance of databases."

"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."

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

"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."

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

"Their support is good, but they can improve their response time."

"Heroku should increase its slug size limits."

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

"Heroku doesn't support Docker images on the CI infrastructure."

"We would like to be notified when something goes wrong in the process. When something is not working, we should get an alert."

"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 had an authentication problem a few months ago, but they solved it."

"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."

"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."

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

"The tool is free."

"Its price is very good."

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

"The price of Heroku could be less expensive."