Home/ Questions/Q 816797
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T01:53:38+00:00

I am trying to implement a real-time application which involves IPC across different modules.

  • 0

I am trying to implement a real-time application which involves IPC across different modules. The modules are doing some data intensive processing. I am using message queue as the backbone(Activemq) for IPC in the prototype, which is easy(considering I am a totally IPC newbie), but it’s very very slow.

Here is my situation:

  • I have isolated the IPC part so that I could change it other ways in future.
  • I have 3 weeks to implement another faster version. ;-(
  • IPC should be fast, but also comparatively easy to pick up

I have been looking into different IPC approaches: socket, pipe, shared memory. However, I have no experience in IPC, and there is definitely no way I could fail this demo in 3 weeks… Which IPC will be the safe way to start with?

Thanks.
Lily

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Been facing a similar question myself.

    I’ve found the following pages helpful – IPC performance: Named Pipe vs Socket (in particular) and Sockets vs named pipes for local IPC on Windows?.

    It sounds like the concensus is that shared memory is the way to go if you’re really concerned about performance, but if the current system you have is a message queue it might be a rather… different structure. A socket and/or named pipe might be easier to implement, and if either meets your specs then you’re done there.

    • 0