We performed a comparison between AWS Fargate and Heroku based on real PeerSpot user reviews.
Find out what your peers are saying about Amazon Web Services (AWS), Apache, Zadara and others in Compute Service."I like their containerization service. You can use Docker or something similar and deploy quickly without the know-how related to, for example, Kubernetes. If you use AKS or Kubernetes, then you have to have the know-how. But for Fargate, you don't need to have the know-how there. You just deploy the container or the image, and then you have the container, and you can use it as AWS takes care of the rest. This makes it easier for those getting started or if you don't have a strong DevOps team inside your organization."
"The most valuable feature of Fargate is that it's self-managed. You don't have to configure your own clusters or deploy any Kubernetes clusters. This simplifies the initial deployment and scaling process."
"Fargate itself is a stable product. We are quite satisfied with its performance."
"We appreciate the simple use of containers within this solution, it makes managing the containers quick and easy."
"If you create your deployment with a good set of rules for how to scale in, you can just set it and forget it."
"AWS Fargate has many valuable services. It does the job with minimal trouble. It's very observable. You can see what's going on and you have logs. You have everything. You can troubleshoot it. It's affordable and it's flexible."
"The most valuable feature of AWS Fargate is its ease of use."
"Valuable for us was the fast deployment. This means the time to market is improved without pain for developers."
"One of the best things about Heroku is that it is very easy and straightforward to deploy an application."
"The platform is very Node.js-friendly, which is something that is important to us."
"Thanks to Heroku, we don't need to do as much direct management in AWS."
"It's easy to push a change and to deploy new things."
"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."
"We use Heroku to run generic data. We also use it for our customer development environment. It helps us to build and test websites."
"What I found most valuable about this solution is that it's easy to use and integrate with GitHub actions."
"AWS Fargate could improve the privileged mode containers. We had some problems and they were not able to run."
"We faced challenges in vertically scaling our workload."
"We would like to see some improvement in the process documents that are provided with this product, particularly for auto-scaling and other configuration tools that are a bit complicated."
"I heard from my team that it's not easy to predict the cost. That is the only issue we have with AWS Fargate, but I think that's acceptable. AWS Fargate isn't user-friendly. Anything related to Software as a Service or microservice architecture is not easy to implement. You're required to have DevOps from your side to implement the solution. AWS Fargate is just a temporary solution for us. When we grow to a certain level, we may use AKS for better control."
"The main area for improvement is the cost, which could be lowered to be more competitive with other major cloud providers."
"If there are any options to manage containers, that would be good. That relates more to the cost point. For example, over the next three months, I'll be making a comparison between solutions like CAST AI and other software-as-a-service platforms that offer Kubernetes management with an emphasis on cost reduction."
"I would like to see the older dashboard instead of the newer version. I don't like the new dashboard."
"Heroku had an authentication problem a few months ago, but they solved it."
"We have to do daily restarts of some processes, which is annoying, and the support for custom CI could be better."
"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."
"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."
"The tool's configuration is complex."
"They could flesh out some of their analytics a little more."
"Their support is good, but they can improve their response time."
"We would like to be notified when something goes wrong in the process. When something is not working, we should get an alert."
AWS Fargate is ranked 6th in Compute Service with 7 reviews while Heroku is ranked 13th in PaaS Clouds with 27 reviews. AWS Fargate is rated 8.8, while Heroku is rated 8.4. The top reviewer of AWS Fargate writes "Offers serverless capabilities, self-managed, simplifies ease of use and integrates with other AWS services". On the other hand, the top reviewer of Heroku writes "Useful for mobile and web applications, and helps with rapid development cycle ". AWS Fargate is most compared with Amazon EC2 Auto Scaling, Amazon EC2, AWS Lambda and AWS Batch, whereas Heroku is most compared with Microsoft Azure, Google Cloud, Google App Engine and OpenShift.
We monitor all Compute Service reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
