I think the most immediate downside of Heroku is that the free tier comes with one dyno that must be booted back up after a short period of inactivity. In other words, the first user to visit your website in a while has to endure the wait until the dyno is spun back up.
Once you cough up the $35/month minimum for an extra dyno, then both dynos stay on. Just something to keep in mind when you're comparing practical price points.
I really appreciate the thoroughness, like the delegation, the metaprogramming, and including the HABTM example from the other Railscast. Just became a subscriber and this cast was instantly actionable.
One of my favorites is Katrina Owen's "Therapeutic Refactoring": http://www.youtube.com/watch?v=J4dlF0kcThQ
I think the most immediate downside of Heroku is that the free tier comes with one dyno that must be booted back up after a short period of inactivity. In other words, the first user to visit your website in a while has to endure the wait until the dyno is spun back up.
Once you cough up the $35/month minimum for an extra dyno, then both dynos stay on. Just something to keep in mind when you're comparing practical price points.
Well, there's also the fact that server rendering is holding up a blocking request. Time/throughput is more expensive than memory.
It's January 2012 and this comment still delivers.
I really appreciate the thoroughness, like the delegation, the metaprogramming, and including the HABTM example from the other Railscast. Just became a subscriber and this cast was instantly actionable.