3. Append the socket remote address to a the message
3. Write message to a queue on an MOM (Asynchronous) -> Messages sent here are processed by other services in the system
4. TCP Server wait for response on it's own queue -> The server has an embedded queue consumer
5. On a receiving message in the TCP queue we read the socket address that was appended at step 3
6 Use a ChannelMatcher to retrieve original socket from the ChannelGroup and write message to the socket
We are anticipating 400 TPS to hit the server , would the channel group be a bottle neck since it's shared byall multiple threads ?