AWS Fargate vs Heroku comparison

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

"By using a server's compute resources, one can observe the resource metrics. With AWS, one can determine when servers will be used based on CloudWatch results. For example, CloudWatch informs the application and service platform when the hit ratio has reached the threshold value."

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

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

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

"AWS Fargate automatically scales to meet demand, making it ideal for applications with variable workloads."

"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 is a fully managed service, and it's very easy to use compared to other services like Elastic Beanstalk Service (EBS)."

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

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

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

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

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

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

"The product is stable."

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

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

"There is a tool named Compose that helps in converting the Docker Compose file into a Kubernetes file. For ECS and Fargate, AWS reads a Dockerfile and helps with conversion. However, I am uncertain if it's ready for deployment after conversion."

"Challenges include higher costs for smaller clients, limited control over underlying infrastructure customization, and potential latencies during task startup."

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

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

"As I have not worked with Fargate extensively, I do not have any specific improvements."

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

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

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

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

"Heroku should increase its slug size limits."

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

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

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

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

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

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

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

"The price of Heroku could be less expensive."

"The tool is free."

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

"Its price is very good."