41–50 of 76 posts
TurboGears, web.py, and Pylons failed the test.
The Python community would benefit from more people switching to Django. It does have the approval of the BDFL, after all.
Earlier quoted context omitted.
* squid reverse proxies * memcached * low memory footprint httpd serving static content (e.g. nginx / lighttpd etc.)
Why squid instead of varnish?
Thanks for the resource. This will come in handy.
Wait... there are people who wrote their own framework... in the year 2009?
Wait... there are people who wrote their own framework... in the year 2009?
Frameworks are great up to a point. If you burger flip web sites all the time, then they make your life easy.
If you only deal with one site, you will never get the flexibility of pure WSGI with some prefabricated framework.
Would someone that up'd Django please outline their plans to scale?
Ellington, which is a Django based CMS runs the Washington Post web site: http://www.ellingtoncms.com/ I don't have doubts about Django scaling. The caching framework is really cool. I did a test a couple of weeks ago, and I got a 10x performance boost, simply by sprinkling 3-4 lines of caching code to my site. That was justing the local memory caching: http://docs.djangoproject.com/en/1.0/topics/cache/#local-mem...…
Would someone that up'd Django please outline their plans to scale?
Ellington, which is a Django based CMS runs the Washington Post web site: http://www.ellingtoncms.com/ I don't have doubts about Django scaling. The caching framework is really cool. I did a test a couple of weeks ago, and I got a 10x performance boost, simply by sprinkling 3-4 lines of caching code to my site. That was justing the local memory caching: http://docs.djangoproject.com/en/1.0/topics/cache/#local-mem...…
Signed, the guy who introduced Django to washingtonpost.com
Earlier quoted context omitted.
Ellington, which is a Django based CMS runs the Washington Post web site: http://www.ellingtoncms.com/ I don't have doubts about Django scaling. The caching framework is really cool. I did a test a couple of weeks ago, and I got a 10x performance boost, simply by sprinkling 3-4 lines of caching code to my site. That was justing the local memory caching: http://docs.djangoproject.com/en/1.0/topics/cache/#local-mem...…
Caching != Scaling
I'm not disagreeing that scaling isn't only caching, but it's often a component just like anything else. Caching often helps scaling, as do multiple databases, working out bottlenecks in code...whatever else.
Am I the only one who likes CherryPy?
Its HTTP implementation is top notch, its tool system is a great way to write custom modules, it has excellent WSGI support, and it's just about the fastest HTTP server in Python that takes a thread-based concurrency approach.
I was the first engineer hired on a team that built an online survey-research company. We started using twisted/nevow, but eventually moved to an in-house web framework on written on CherryPy. Lots of tools have come and gone (mostly, we've rewritten components we found lacking) but CherryPy has never let us down. We even ended up hiring a large portion of the CherryPy team.
Our experiences with it were positive enough that I'm building a startup right now on a similar CherryPy-based stack (at least partially--there's also a bit of Erlang involved for the high-concurrency stuff).
If you're considering stitching together your own Python Web framework--as many shops eventually do--I highly recommend CherryPy be used as the foundation.
Am I the only one who likes CherryPy?
CherryPy is a hugely underappreciated project in the Python community. Its HTTP implementation is top notch, its tool system is a great way to write custom modules, it has excellent WSGI support, and it's just about the fastest HTTP server in Python that takes a thread-based concurrency approach. I was the first engineer hired on a team that built an online survey-research company. We started using twisted/nevow, but…
All the above being said, it's only fair to acknowledge that this isn't quite apples-to-apples when you look at CherryPy vs. something like Django. CherryPy isn't really a full-stack web framework, it's an HTTP server attached to a configuration and tool system that facilitates the creation of custom web frameworks.