Related to bbcarchdev/libcluster#15
By allowing an instance of an application to specify a (named) partition that it is operating as a part of, an MQ engine can filter messages based upon this partition, allowing more for complex processing topologies than a simple queue.
For example—depending upon the engine’s implementation—messages might be tagged with a partition based upon a regular expression match on the sender's address, or content type, and then this partition name can be used by the receivers to direct different sources or types of message to different groups of processing nodes.
In effect, it allows an engine to support groups of logical related queues which are fed and used in a unified fashion.
Related to bbcarchdev/libcluster#15
By allowing an instance of an application to specify a (named) partition that it is operating as a part of, an MQ engine can filter messages based upon this partition, allowing more for complex processing topologies than a simple queue.
For example—depending upon the engine’s implementation—messages might be tagged with a partition based upon a regular expression match on the sender's address, or content type, and then this partition name can be used by the receivers to direct different sources or types of message to different groups of processing nodes.
In effect, it allows an engine to support groups of logical related queues which are fed and used in a unified fashion.