Deprecated: Function get_magic_quotes_gpc() is deprecated in /home/styllloz/public_html/qa-include/qa-base.php on line 1175

Warning: session_start(): Cannot start session when headers already sent in /home/styllloz/public_html/qa-include/app/users.php on line 162

Warning: Cannot modify header information - headers already sent by (output started at /home/styllloz/public_html/qa-include/qa-base.php:1175) in /home/styllloz/public_html/qa-include/app/users.php on line 1267

Warning: Cannot modify header information - headers already sent by (output started at /home/styllloz/public_html/qa-include/qa-base.php:1175) in /home/styllloz/public_html/qa-include/app/page.php on line 356
Collector/distributor message, aka "message broker"? - | Q&A

Collector/distributor message, aka "message broker"?

Warning: count(): Parameter must be an array or an object that implements Countable in /home/styllloz/public_html/qa-theme/donut-theme/qa-donut-layer.php on line 274
0 like 0 dislike
There is a need to develop a middleware module: the collector/distributor message, aka "message router", "message broker", "message orientated middleware". For big names in the current implementation — simple essence: clients send messages (asynchronously), the message comes to the broker and (while I call the required collector/distributor), he somehow handles and holds up to the moment it asks for the message recipient (the one to whom it was intended).

The recipient requests the message, the message transmitted to the recipient – all, the job broker and over.

The first idea is to implement a broker to use for storing memory were rejected, because the recipient is irresponsible, not taking data, make the broker eat all the memory.

The second is to use a database to store messages when "intensive" the receiver will always generate DB queries.

The final (current) option – memory use for a queue of references to messages stored in non-SQL database (of the advantages – requires no configuration database of the drawbacks – not enough quick start (read queue are stored at the time of the stop), and sensitivity to a regular stop (can not be recorded the current queue)).

Interested in the question, who created a similar solution?

The requirements are simple:

  1. small memory consumption
  2. quick start
  3. the ability to handle messages of large size, with a small quantity of the messages themselves
  4. preferably no need to create a database

Since the requirements are rather contradictory – on display in the descending order of priority.

Also interested in the question of the impact of messages to a recipient who uses what steps (notification of the processing, the periodic survey, subscribe to a message type, etc....)

PS: Finished software products are inappropriate as they require additional resources, settings, and suggest that the architecture will be built around them, and for me it's just a means of creating asynchronous messaging — then perhaps it will be merged into 1. exe file.
by | 7 views

2 Answers

0 like 0 dislike
Redis publish/subscribe?
0 like 0 dislike
beanstalkd — what you need

Related questions

0 like 0 dislike
2 answers
0 like 0 dislike
1 answer
0 like 0 dislike
1 answer
0 like 0 dislike
4 answers
asked Mar 28, 2019 by ProotIK
110,608 questions
257,186 answers
35,181 users