AWS Fargate vs Heroku comparison

"The most valuable feature of AWS Fargate is its ability to run on demand without the constant run time of basic resources."

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

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

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

"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 automatically scales to meet demand, making it ideal for applications with variable workloads."

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

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

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

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

"The product is stable."

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

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

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

"There are features that could be added or enhanced."

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

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

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

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

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

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

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

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

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

"The pricing could be improved because scaling the database becomes costly."

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

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

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

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

"The price of Heroku could be less expensive."

"Its price is very good."

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

"The tool is free."

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