I originally started unscatter.com on Tornado, then got caught up in the whole node.js spin. I started rewriting the application using node.js, then realized I

I originally started unscatter.com on Tornado, then got caught up in the whole node.js spin. I started rewriting the application using node.js, then realized I was rewriting large chunks of Tornado in javascript. I went back to Tornado and have since put up something that works, very quickly. I use supervisord for maintaining multiple instances of the application running. I found it the simplest way to manage it. It also gave me support for watching and restarting any instances that hang. I'm also using nginx to proxy. Currently I'm proxying 2 instance of tornado on a 4 core box. I'm also running mongodb, memcached, and nginx on the same small 256MB ram box right now. In the future I could see me moving to node.js in the future, but for any application that requires working with multiple APIs, Tornado was a much better headstart, and the framework itself was more mature and ready to use than anything from the node.js camp several months ago. Unfortunately no one is actively supporting the auth portion of Tornado, and it could use a maintainer. I'd set up, but with a newborn I'm not sure when I'll get to it. I'll be releasing ( and have already done so in the past ) any changes I make back to the Tornado project.