Hacker News Reader

Django (and pretty much any other framework) is usually "fast enough"; typically you'll hit the limits of your datastore first, and even if you reach the point where the framework becomes an issue it's trivial to scale horizontally due to its stateless nature.

View on HN

Yup, same story on Ruby/Rails. Yes, its true that our median response times could be faster if we spent less time on Ruby CPU burn. But its also true that this improvement would still be a rounding error for many of our slowest requests, which are dominated by calls to databases, external services over HTTP, or both.

I hear this all the time but in most of our apps average query time is less than 5ms in postgres. And it scales with threads, so it's more like 30k queries per second.

We have a single Postgres instance and serve thousands of requests per second. You're going to be scaling Django way before that.

Reply on news.ycombinator.com