The Heroku Platform, now from Salesforce, is a platform-as-a-service based on
a managed container system, with integrated data services and ecosystem for deploying modern apps. It takes an app-centric
approach for software delivery, integrated with developer tools and
workflows. It’s three main tool are: Heroku Developer Experience (DX), Heroku
Operational Experience (OpEx), and Heroku Runtime.
Heroku Developer Experience (DX)
Developers deploy directly from tools like…
$25
per month
IBM Cloud Code Engine
Score 9.4 out of 10
N/A
IBM Cloud Code Engine is a fully managed, serverless platform that unifies the deployment of containers and applications including web apps, microservices, event-driven functions, or batch jobs. This serverless compute service aims to remove the burden of building, deploying, and managing workloads in Kubernetes so users can focus on writing code and not on the infrastructure that is needed to host it. With IBM Cloud Code Engine users can run any workload…
Heroku was more extensive in terms of its operating and scaling from what we witnessed by looking into other options and trying to find the best operating system for a new platform.
Heroku Platform is cheaper to begin with compared to DigitalOcean or Amazon Fargate. The configuration user interface is also arguably easier to understand. With its user friendliness and cheaper tiers, Heroku Platform was our pick to host some of our applications that were …
I believe Azure App Service is pretty similar to Heroku as you can in both deploy your backend applications. However, the dyno concept and it's drastically simple web dashboard makes Heroku a much better and sane alternative to Azure app service. In Heroku, you get abstracted of …
Kuberbetes is an easily scalable docker based option which should need minimal DevOps, however, it has a pretty high learning curve with many decisions that need to be addressed as well as monitoring, logging and security concerns.
Heroku has the advantage of simplifying the development and integration with some services (which in Heroku they call addon) wherein other platforms, certainly for those who don't have much experience, it will take much more development time.
Heroku, in my opinion, is the easiest platform to deploy and host web applications on. From collaboration to deployment, everything is well thought out and bulletproof. If you need advanced server functionality, like a VPC, machine-to-machine communication, etc., you will …
We also use Cloud 66 which provides some of Heroku's features, at a lower price. It still cannot compare to Heroku's ease of use and ability to easily deploy new staging environments though, so we will always use Heroku for at least some of our projects.
Heroku is an all in 1 package for deploying and running your services. It provides an easy to use setup and run for 90% of cases. If you have a more complicated infrastructure, you'd definitely need to move to another hosting provider. But if as long as you can operate within …
Heroku has advantages over Docker, Google App Engine and AWS products, but it depends largely on your use case. If you are already in AWS, it's probably in your best interest to stay with AWS products. However, other "Cloud Formation/Orchestration" products like Docker are …
We kicked the tires on OpenShift before deciding on Heroku, and found the platform to be much less intuitive and well-documented than Heroku. It felt like we were constantly trying to implement workarounds for esoteric platform problems, and eventually the work became too …
For a different project, Aptible surpassed Heroku when it came to meeting HIPAA-related requirements, though it offers much less flexibility with add-on services (for obvious reasons). Google App Engine had a much more complicated deployment model and seemed unnecessarily …
To this day no other PaaS matches Heroku in ease of use and maturity. If you want to stay 100% focused on your unique product/service rather than wasting time on boilerplate hosting issues, I can highly recommend Heroku. I personally use it for all of my own websites …
Heroku is the more expensive option for hosting compared to some of the cloud platforms we investigated, but it's worth it for us because of the plug-and-play nature of Heroku deployment. We can be up and running in a few minutes and know with precision how much it will cost us …
Heroku has the easy facility to deploy and host applications while others have to configure a lot. The price of the services is high for others. But within Heroku pricing and easy to maintain under the same roof.
Some APIs are specifically developed to be deployed to certain platforms and usually decision which platform to use is not developer's. Another question is deployment cost and pricing model; in specific cases after price comparison Heroku is often selected among other cloud …
Heroku is a really great platform to get up and running QUICKLY and efficiently. What Heroku is really great at that other services are lacking is ease of use, documentation. It is really great for beginning developers and awesome to get up and running to take care of lots of …
I feel Heroku is lightyears ahead of all other PaaS offerings. To me the competition is between PaaS and self-hosted cloud, not between Heroku and other PaaS providers.
IBM Cloud Satellite is distributed cloud platform while IBM Code Engine is serverless. They both has capabilities that are non overlapping and run on IKS/K8S.
What impresses me most about IBM Cloud Code Engine is the container workload management capability and the Cloud services and dataflow monitoring functionalities. Data security and network security control via IBM Cloud Code Engine is quite excellent and very responsive data …
If IBM wants to get ahead, it needs to add AI and make it seamless on the project configuration, real time chat with AI will help developers to increase speed and have less problems integrating the code into their business logic. There's no marketing using influencers, YT code …
Having only some hands-on with the other services, The cloud engine is considerably simpler to operate, with a very clear interface and management. Each application can be easily configured and altered without needing to know anything about different subscription tiers or the …
Cloud engine is much easier to use, and gives a very clear interface and control. Each application can be configured differently with ease and changed without having to know anything about different subscription levels or inner workings of the system. Just change the resource …
During software selection is always good to give different weight to each parameter of evaluation. Usually cost and performances are always having higher weight, but it's good not forget about support and integration. A scenario with a great tool, impossible to integrate in the …
Heroku is very well-suited to early stage and/or rapidly changing projects. It is great for getting moving quickly or changing direction quickly. In scenarios where there is already scale or well-defined requirements, it may be preferable to set things up directly on AWS or another cloud provider to avoid the additional costs of Heroku as the middleman.
Looking for a reasonably priced and dependable cloud solution, I suggest IBM Cloud Virtual Servers to everyone. For businesses needing excellent uptime and performance free from the trouble of running actual servers, it's fantastic. However, it may not be the best choice if you need hands on support for server configurations.
Could be less expensive, although you get what you pay for
Sleeping apps can be an annoyance: Heroku automatically puts your apps in sleep mode and they have to spin back up after periods of inactivity. Much of this can be solved but it requires working around the built-in functionality. I understand why they do it but it's an area that could be improved.
Restrictions to server access means you can't customize as much as you could if you owned the server. But again, this is also a benefit because it's about convention over configuration. So you can't configure as much, but then, you typically don't have to.
the pricing structure is complicated, and the servers are expensive. I really think they should offer better pricing options and support for more languages
sometimes the servers go down, and they take too long to respond to support tickets
uploading documents is slow since I have to do it one by one, making the process much longer than it should be
Heroku is a critical and core part of our infrastructure that is serving our customers well. We are very satisfied with the cost of our solution. While it would be difficult to move away from Heroku, we have no plans to do so. We have had no major issues with it and it is a pleasure to use. Other products on the market might offer comparable functionality, but until we expose a need that Heroku cannot satisfy, we'll stay the course.
If you have basic backend and Git knowledge, deploying to Heroku is a breeze. It now supports many types of backends, including hybrid backends (ex: nginx + application server) through its build pack system. The dashboard is easy to use, and the CLI tools are well designed. Accessing the add-ons is also easy. It uses an SSO-type system so you don't have to re-sign in to view the add-on dashboards.
The product Cloud features setting was not that tricky, and the functions are easy to manipulate and provide quality Cloud services. The data connectivity through IBM Cloud Code Engine is very simple and the transfer speed is very impressive. A/B Testing using IBM Cloud Code Engine is effective performed and data security is on top.
Heroku availability correlates pretty strongly to AWS US EAST availability. We had a couple of times where there was a Heroku-specific issue but not for the last 7-8 months.
I've used it for many years without facing any major problem. It's not hard at all to get used to it, it's documentation is outstanding and simple. We are close to 2020 and I don't think most of the existing companies or startups should still face old problems such as wasting time deploying code and calculate computing resources.
Be ready to pay a bit more than expected in the beginning if you're migrating from a big server. The application is probably not ready for the change and you have to keep improving it with time.
It's also important to consider that you can't save anything to the disc as it will be lost when your application restarts, so you have to think about using something like S3.
Heroku has advantages over Docker, Google App Engine and AWS products, but it depends largely on your use case. If you are already in AWS, it's probably in your best interest to stay with AWS products. However, other "Cloud Formation/Orchestration" products like Docker are typically lacking the ease-of-use factor that allows you to get up and running with Heroku quickly.
Having only some hands-on with the other services, The cloud engine is considerably simpler to operate, with a very clear interface and management. Each application can be easily configured and altered without needing to know anything about different subscription tiers or the system's inner workings. But in the case of Lambda, Depending on the situation, Code Engine will fetch your source code and generate the container image. Code Engine supports both Dockerfile and the Cloud-Native Build bundle, which is preferable. It is possible to create applications that send messages based on events.
IBM maintains the same high degree of security that has been essential for its operations since the dawn of the computing market while streamlining data governance in a real cloud model as a dependable business partner for organizations all across the globe.
Apart from providing the instruments needed for efficient work the user friendly interface helps non-IT professionals to understand the system in a limited period of time.
The latest IBM Cloud Code Engine design is based on an innovative approach to buying and bundling of products.