Introducing Improved Performance Dynos
blog.heroku.com
Introducing Improved Performance Dynos
1–5 of 5 posts
Re: Introducing Improved Performance Dynos
#2Re: Introducing Improved Performance Dynos
#3It seems like the hype around Heroku has died down somewhat. Does anyone care to comment why they went with Heroku vs. AWS or the like?
As your systems get more complex, you can still peel off services to AWS or the like, but until then, Heroku combines the following tasks and AWS services into a dead simple process: configuring instances, Scaling Groups, RDS, Cloudwatch (some metrics, consolidated logging) and ELB.
Re: Introducing Improved Performance Dynos
#4It seems like the hype around Heroku has died down somewhat. Does anyone care to comment why they went with Heroku vs. AWS or the like?
I would argue that Heroku is still the fastest way to get a web app deployed for the first time. One command to push and one click to setup a solid database. As your systems get more complex, you can still peel off services to AWS or the like, but until then, Heroku combines the following tasks and AWS services into a dead simple process: configuring instances, Scaling Groups, RDS, Cloudwatch (some metrics, consolida…
Re: Introducing Improved Performance Dynos
#5It seems like the hype around Heroku has died down somewhat. Does anyone care to comment why they went with Heroku vs. AWS or the like?