DevOps Django - The Heroku Way | Hacker News Reader

DevOps Django - The Heroku Way

rdegges.com

Or you could use ep.io, which is comparably awesome and boasts a generous free _per-app_ quota. Either way, these services are great for django. Yay!

Not disagreeing with you here at all--however, Heroku also has a generous free tier for their core services (and most addons).

In the next part of the series I'm going to elaborate on their pricing in comparison to Rackspace for my work project. Heroku is actually significantly cheaper for us, considering we don't have to spin up additional instances for backups, load balancing, etc.

FYI, Heroku also offers 750 free hours per-app.

To elaborate on this: that's enough to run an entire website for free (excluding celery).

If you want to run a celery worker (including beat), you're looking at a total cost of 30$ per month. That's enough for most moderate traffic websites. :)

Of course you can run celery within the same process too.

Our process model is really only measuring application entry-points. You could have your free "process" spin off 10 other subprocesses beneath it. The only constraint is RAM.

Is heroku's free instance loaded on demand? If not that would be cool as startup times on the ep.io dynamic instances are v slow.

What do you mean by loaded on demand? You can instantly scale up and down the amount of workers you have, if that's what you mean.

I've been scaling mine around, and it's never taken more than a second or two. Although, maybe that would change if you are scaling up to hundreds of workers or something like that.

He probably asks if they are pre-loaded (so when someone first visits your webpage they don't have to wait for the django config to be parsed and it get loaded onto memory).

It's common in free versions of such services, to only load things on demand, which is a little slow --in Google App Engine you can pay to have instances pre-loaded.

Oh. Yes, they are identical to paid dynos. Essentially, Heroku just deducts 750 paid hours from your bill each month (which is just enough to run one web dyno 24x7).

ep.io's hardware is in Europe. Is the increased latency a legitimate concern for a startup that only serves US customers?

I have a few small things on ep.io right now, and it's great.

This came just in time for me : I need to post up REST demo django app, and was considering taking the dive into Heroku. You've convinced me to jump.

Thanks.

Reply on news.ycombinator.com