[agallego]

Very similar :)

We do use a proxy/router. The main difference is that instead of using etcd for service discovery we are deeply integrated with Mesos.

Our framework scheduler does the registration/deregistration, resource allocation/colocation, etc.

The main reason for a proxy at this point is to have unified metrics collection, distributed routing (each reverse proxy knows only its immediately connected downstream operators), tracing (think dapper), and facilitating the communication with other languages (c++, java, go, js - node, ruby, etc).