linux - Using loopback interface for communicating between production application -


i developing 2 applications on ubuntu server needs communicate each other on udp @ peak 200 mbps. in initial stage planning deploy both applications on same server communicating on loopback-address.

i have 2 concerns setup. appreciated.

  1. is practice use loopback interface communicating between 2 applications.
  2. is there performance limitation in maximum throughput can achieved loopback interface.

using loopback (127.0.0.1) interface developmental (debugging) increment network enabled/aware application. if you're using loopback interface solely ipc (inter-process communication) vehicle, i'd "raise eyebrow". additionally, data throughput (200 mbps peak concern) doesn't transmit (through osi physical layer) , "turned around" within network layer. (two) questions:

  1. in context of debugging network aware/enabled application, preferred way test both client(s) / server on same device. means of ipc, adds unnecessary overhead marshaling data between processes if desired objective, i'd @ os-indigenous ipc mechanism (as translates memory-mapped files cross process boundaries; can efficiently configured memory-resident , fast).

  2. performance relative udp design. size of payload, structure of messages, queue management, etc. deal normal network stack overhead of course (but there less overhead in ipc mechanisms if implemented , applicable).

let me know if you're looking specific code fragments or general question (as i've read as). hope helps.


Comments

Popular posts from this blog

javascript - Bootstrap Popover: iOS Safari strange behaviour -

Magento/PHP - Get phones on all members in a customer group -

session - Logging Out Using PHP -