The MongoD process should open a second listening port to receive requests which will be routed (by the embedded router) to the proper shards.

The characteristics of this port should be the same of the one opened by the MongoS (i.e., default port number, limit on the connections, etc.). The MongoD executable should accept the expected arguments to customize that port behaviour.

As a consequence, operation contexts and clients should have a getter function to determine the origin of the request, i.e., from router or shard port.

On the other hand, the standalone router (i.e., MongoS) should mark operation contexts and clients accordingly (from router by default).