Amazon Elastic Container Service (Amazon ECS) vs Heroku Platform

• One of the biggest advantages is the flexibility to change underlying EC2 instances. As the traffic or demand increases, we can easily change EC2 instances without any issues.
• Amazon ECS APIs are extremely robust and one can start and stop containers by firing one post request only. So, it is not mandatory to keep the demo solutions up for every time. Just at the time of demo fire the command - make the container up and running - do the demo - down the container with API. A simple portal can control every container which helps non-technical (sales, marketing) to do the demo without keeping the solutions up for the entire time frame.

Read full review

• Heroku has a very simple deployment model, making it easy to get your application up-and-running with minimal effort. We can focus on our efforts the unique aspects of our application.
• The robust add-on marketplace makes it easy to try out new approaches with minimal effort and investment -- and when we settle on a solution, we can easily scale it.
• Heroku's support is quite good -- their staff is quite technical and willing to get into the weeds to diagnose even complicated problems.

Read full review

• There is room for better documentation.
• Is not exactly Kubernetes (there is more knowledge in the market on this orchestrator).
• Logging can be difficult.

Read full review

• Large price jumps between certain resource tiers (2x Dyno for $50 per month versus Performance Dyno for $250). Free Postgres next jumps to $50 per month.
• Marketing/Branding to non-technical stakeholders. As the years pass, I've had to fight more to convince stakeholders on the value of Heroku over AWS.
• Improve Buildpack documentation. This is one area where Heroku's documentation is fairly confusing.

Read full review

• We run 8 web applications (demo instances) on a single machine. At a particular time, no more than 3 applications run simultaneously. So, we keep only required containers up. This helps us to provision small EC2 machines without compromising performance.
• Overall Amazon ECS helps to have less number of dedicated machines as more than one solution can be deployed on a single instance. This reduces costs a lot.

Read full review

• Heroku allowed us to get up and running fast. Deployment was really easy and connecting to our codebase was, too. The deployment integration with GitHub is pretty slick.
• The add-ons provisioning is so simple and the documentation is so thorough that, at least at first, it means you don't have to hire a dedicated devops person to manage this stuff.
• Heroku has tools that allow the collaborators (those with access to the Heroku dashboard) to be able to quickly and easily do triage from just about anywhere, including your smartphone.

Read full review