An interesting tool for those needing a way to process the CouchDB _changes server-side:
However, one thing that’s missing is being able to write some code in your design document that consumes these changes on the backend and doesn’t depend on another active client. To remedy this situation I decided to write a generic change consumer that you could point at CouchDB and it would find any change handlers in any of the design documents and keep them running, consuming changes, and removing or replacing them when the design document changed.
In the past we’ve also seen how to use RabbitMQ to push notifications from _changes, but both these solutions may prove quite useful.
Other CouchDB tips&tricks