11–20 of 39 posts
Earlier quoted context omitted.
Heroku is really just AWS with convenience, isn't it? I'm not sure what else they do - but I guess that "convenience" is worth it for some.
Is it possible to launch using just a single dyno and heavy caching/optimization?
Earlier quoted context omitted.
Is it possible to launch using just a single dyno and heavy caching/optimization?
They will shut down your instance, if you don't use it for an hour or two - and then it will take like 8-10 seconds to load it again. If you can live with that, I guess that would work, yes.
Just curious, thanks!
Earlier quoted context omitted.
They will shut down your instance, if you don't use it for an hour or two - and then it will take like 8-10 seconds to load it again. If you can live with that, I guess that would work, yes.
There are very, very easy ways around this.
I'd love to deploy on Heroku, but it's so dramatically more expensive than aws. For a startup, is it really worth that additional cost?
Heroku is really just AWS with convenience, isn't it? I'm not sure what else they do - but I guess that "convenience" is worth it for some.
I would really like to see more details about their architecture, especially about the MongoHQ integration.
No offense to the Art.sy team, but this is just Heroku marketing copy. It lacks the detail we typically see on these sorts of high scalability "how we did it" posts. Non-trivial applications scale non-trivially, and when someone comes along claiming they have solved the scalability problem with the push of a button I am instantly skeptical. I would really like to see more details about their architecture, especially…
Our MongoHQ integration is very straightforward - MongoHQ provides us with a replica set and we configure it as any other MongoDB database.
Feel free to ask any specific questions.
Earlier quoted context omitted.
There are very, very easy ways around this.
One being a service like http://uptimerobot.com/ that pings the site every 5 minutes
I'm just curious, how much traffic NYTime brought you guys. I'm also on Heroku and my app( http://www.tubalr.com ) "survived" several articles around the web(Mashable, TechCrunch, The Verge, The Next Web, Japan LifeHacker, and several others) within a very short timespan. My bill has never been over $25, which includes no extra workers.. just extra DB storage and an upgraded DNS plugin. Just curious, thanks!
We prepared for the worst, though, and had built a failsafe way to progressively shut off more demanding features on the site (for instance: our related search results on artwork pages) in case we were getting overwhelmed. Much better to have a reduced feature set during launch than a broken site. Fortunately we didn't have to flip that switch!
I'm just curious, how much traffic NYTime brought you guys. I'm also on Heroku and my app( http://www.tubalr.com ) "survived" several articles around the web(Mashable, TechCrunch, The Verge, The Next Web, Japan LifeHacker, and several others) within a very short timespan. My bill has never been over $25, which includes no extra workers.. just extra DB storage and an upgraded DNS plugin. Just curious, thanks!
Art.sy was lucky to be the top article on NYTimes (the one with the large image at the top of their homepage) from about 5pm to 11pm, were the #3 most emailed, and the NYT article was #3 on Hacker News. We went to 1500 concurrents almost instantly, and maintained it for several hours. This is nothing for many large sites, but was the most we'd had. We had added some extra dynos in preparation, and our API response ti…