10 Jan '14, 4am

Moving (again) from Heroku to EC2:

I really love the ease of deployment to heroku and the fact that they manage the whole stack. However I receive regularly emails from Heroku stating that I get a specific number of “backlog too deep errors” indicating the app is receiving more requests than it is capable of responding to, or in other words that that my blog is outgrowing their developer instance. So I have the option to increment the number of requests my application can handle, which is easy thanks to the the heroku command line: heroku dynos +1 —app onrails. So I can increase the HTTP performance by cranking up the “dynos” to 2 which would be an additional $36 a month. I still think it’s a good deal for a managed environment.

Full article: http://onrails.org/2010/09/20/moving-again-http-onrails-o...

Tweets

Moving (again) from Heroku to EC2:

onrails.org 10 Jan '14, 4am

UsageReport Downloader for Amazon Web ServicesTM. A simple tool to download all you usage reports with one click. ec2, s3,...

#BREAKING: USS John Paul Jones to replace USS L...

navy.mil 07 Jan '14, 11pm

CORONADO, Calif. (NNS) -- The U.S. Navy announced Jan. 7, that USS John Paul Jones (DDG 53) will swap homeports with USS L...