AWS Fargate vs Heroku comparison

"Fargate is beneficial for hosting our solutions and providing workflow management, creating legal documents, and delivering business intelligence."

"AWS Fargate is an easy-to-use tool to simplify setup. You only pay for the resources you use. If you need to quickly create, delete, or scale applications without managing resources like EC2 instances, Fargate is the best service to use."

"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 AWS Fargate is its ease of use."

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

"Fargate's integration with other AWS services is really good."

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

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

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

"The product is stable."

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

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

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

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

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

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

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

"AWS Fargate needs improvement in terms of setup complexity."

"We faced challenges in vertically scaling our workload."

"AWS Fargate's security features weren't the most important criteria or value we got from AWS Fargate."

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

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

"I would like to see enhanced faster application scaling and better integration with the elastic file system to unify storage volumes and improve the launch time of instances."

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

"Heroku should increase its slug size limits."

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

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

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

"The tool's configuration is complex."

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

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

"Its price is very good."

"The price of Heroku could be less expensive."

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