message queue - How many tcp connection created on a queuing protocol such as ZeroMQ -


excuse me basic question, didn't find answer in google searches.

i want develop server should respond hundreds of clients. each client may send tens hundreds of messages per second.

i want know if use queuing protocols such amqp (rabbitmq implementation) or zeromq, how many tcp connections server should supports?

is total number of clients or total number of messages per second?

nota bene: zeromq not "queuing"-protocol. 1 shall rather think powerful framework of low-level building blocks [primitives] enable designers setup fast , rather abstract behaviour-oriented designs advanced use-cases messaging per se robust, non-blocking, asynchronous, distributed systems concurrency signalling , content-related transport + controls. indeed powerful set of tools, believe me.

amqp broker-based approach

zeromq broker-less solution

message count per se not typically create problem.

their associated processing typically does.


limit no.1: operating system tcp-settings constraints

solution: review system documentation limits work within , setup/tweak values, on os-level, appropriate.


limit no.2: growing end-point's process delay(s) grows risk of recv/send buffer overflow(s).

solution: review code-architecture whether can increase transaction-performance ( distributed pipe-line processing or load-balancer distribute flow of incoming connections / transactions onto multiple target worker-units ).


Comments

Popular posts from this blog

powershell Start-Process exit code -1073741502 when used with Credential from a windows service environment -

twig - Using Twigbridge in a Laravel 5.1 Package -

c# - LINQ join Entities from HashSet's, Join vs Dictionary vs HashSet performance -