The most complex thing I've done with it is this Twitter client: http://jchris.couchone.com/twebz/_design/twebz/index.html http://jchris.couchone.com/twebz/_des

The most complex thing I've done with it is this Twitter client: http://jchris.couchone.com/twebz/_design/twebz/index.html http://jchris.couchone.com/twebz/_design/twebz/index.html It uses OAuth and all that good stuff. The "fragile" parts are handled by an asynchronous _changes based process (Node.js is a good fit but really anything works). The key is to get anything that could go wrong, out of the request / response loop between the browser and the server. The asynchronous handler pattern is a best practice anyway (resize an image on POST, or in a queue?). Keeping the request / response critical path simple makes for more reliable apps.