Home/ Questions/Q 495225
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T05:34:23+00:00

as opposed to writing your own library. We’re working on a project here that

  • 0

as opposed to writing your own library.

We’re working on a project here that will be a self-dividing server pool, if one section grows too heavy, the manager would divide it and put it on another machine as a separate process. It would also alert all connected clients this affects to connect to the new server.

I am curious about using ZeroMQ for inter-server and inter-process communication. My partner would prefer to roll his own. I’m looking to the community to answer this question.

I’m a fairly novice programmer myself and just learned about messaging queues. As i’ve googled and read, it seems everyone is using messaging queues for all sorts of things, but why? What makes them better than writing your own library? Why are they so common and why are there so many?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    what makes them better than writing your own library?

    When rolling out the first version of your app, probably nothing: your needs are well defined and you will develop a messaging system that will fit your needs: small feature list, small source code etc.

    Those tools are very useful after the first release, when you actually have to extend your application and add more features to it.
    Let me give you a few use cases:

    • your app will have to talk to a big endian machine (sparc/powerpc) from a little endian machine (x86, intel/amd). Your messaging system had some endian ordering assumption: go and fix it
    • you designed your app so it is not a binary protocol/messaging system and now it is very slow because you spend most of your time parsing it (the number of messages increased and parsing became a bottleneck): adapt it so it can transport binary/fixed encoding

    • at the beginning you had 3 machine inside a lan, no noticeable delays everything gets to every machine. your client/boss/pointy-haired-devil-boss shows up and tell you that you will install the app on WAN you do not manage – and then you start having connection failures, bad latency etc. you need to store message and retry sending them later on: go back to the code and plug this stuff in (and enjoy)

    • messages sent need to have replies, but not all of them: you send some parameters in and expect a spreadsheet as a result instead of just sending and acknowledges, go back to code and plug this stuff in (and enjoy.)

    • some messages are critical and there reception/sending needs proper backup/persistence/. Why you ask ? auditing purposes

    And many other use cases that I forgot …

    You can implement it yourself, but do not spend much time doing so: you will probably replace it later on anyway.

    • 0