AWS Fargate vs Heroku comparison

"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 definitely impacted our organization positively because before that, we couldn't accommodate the workload requirements as flexibly as we can with Fargate."

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

"The tool's configuration is complex."

"Heroku should increase its slug size limits."

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

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

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

"The price of Heroku could be less expensive."

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

"Its price is very good."

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

"The tool is free."