Pair protocol is the simplest and least scalable scalability protocol. It allows scaling by breaking the application in exactly two pieces. For example, if a monolithic application handles both accounting and agenda of HR department, it can be split into two applications (accounting vs. HR) that are run on two separate servers. These applications can then communicate via PAIR sockets.
The downside of this protocol is that its scaling properties are very limited. Splitting the application into two pieces allows to scale the two servers. To add the third server to the cluster, the application has to be split once more, say by separating HR functionality into hiring module and salary computation module. Whenever possible, try to use one of the more scalable protocols instead.
Socket for communication with exactly one peer. Each party can send messages at any time. If the peer is not available or send buffer is full subsequent calls to nn_send(3) will block until it’s possible to send the message.
No protocol-specific socket options are defined at the moment.
nn_bus(7) nn_pubsub(7) nn_reqrep(7) nn_pipeline(7) nn_survey(7) nanomsg(7)
nanomsg(7), nn_bus(7), nn_pipeline(7), nn_pubsub(7), nn_reqrep(7), nn_survey(7).