AWS Fargate vs Heroku comparison

"AWS Fargate has definitely impacted our organization positively because before that, we couldn't accommodate the workload requirements as flexibly as we can with Fargate."

"It allows for focusing on applications instead of managing infrastructure."

"All AWS services allow me to manage a wide range of applications and services."

"Fargate itself is a stable product. We are quite satisfied with its performance."

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

"The best thing about AWS Fargate is that I don't need to worry about the proper provisioning of infrastructure for my task, and it's very fast in terms of scaling my containers; it's much faster than other solutions."

"We appreciate the simple use of containers within this solution, it makes managing the containers quick and easy."

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

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

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

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

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

"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 solution's most valuable feature is the auto maintenance of databases."

"I like the tool's scalability, CLI, and dashboards."

"The main area for improvement is the cost, which could be lowered to be more competitive with other major cloud providers."

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

"AWS Fargate could improve the privileged mode containers. We had some problems and they were not able to run."

"There could be improvements for AWS Fargate regarding cost as it is expensive compared to running on EC2."

"I would like to see the older dashboard instead of the newer version. I don't like the new dashboard."

"Sometimes, Fargate can be really hard to configure."

"Service computing is not as straightforward compared to other computing services. It requires more effort to use effectively."

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

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

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

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

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

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

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

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

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

"We would advise that this solution has a slightly-higher price point than others on the market. There is a free plan available for start-ups, but the free and lower range licensing models do not provide the full functionality."

"I rate the price of AWS Fargate a four out of five."

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

"The tool is free."

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

"The price of Heroku could be less expensive."

"Its price is very good."