400 TPS per second is not really much. So no… That said you will need to do some benchmarks by yourself.
> On 24 Aug 2016, at 00:48, Kimathie <[email protected]> wrote: > > Sorry Norman I have hadn't finished typing this question and It wasn't meant > to be sent. But now that it is here let me just ask > > Good day, > I am working on a design for a TCP Server. The server is meant to for > handling transaction requests only at high volumes. > To explain the design > 1. Add socket to ChannelGroup > 2. Read message from the Socket > 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 ? > > > > On Friday, 22 July 2016 16:55:19 UTC+3, Norman Maurer wrote: > An what is the question here ? > > >> On 18 Jul 2016, at 14:02, Kimathie <[email protected] <javascript:>> wrote: >> >> Good day, >> I am working on a design for a TCP Server. The server is meant to for >> handling transaction requests only at high volumes. >> To explain the design >> 1. Add message to DefaultChannelGroup >> 2. Read message from the Socket >> 3. Write message to a queue on an MOM (Asynchronous) >> >> 4. System to write Wait for response on queue with a couple of consumers >> registered >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Netty discussions" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/netty/e651e821-6e59-40c9-98ca-838f1c9ae51b%40googlegroups.com >> >> <https://groups.google.com/d/msgid/netty/e651e821-6e59-40c9-98ca-838f1c9ae51b%40googlegroups.com?utm_medium=email&utm_source=footer>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to the Google Groups > "Netty discussions" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/netty/01481ded-4157-4851-9a30-3d667c41954b%40googlegroups.com > > <https://groups.google.com/d/msgid/netty/01481ded-4157-4851-9a30-3d667c41954b%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Netty discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/netty/543ECDC0-EED8-451C-A50F-EC9E7B12F9B0%40googlemail.com. For more options, visit https://groups.google.com/d/optout.
