In many architectural scenarios, if application A needs to send updates or commands to applications B and C, then separate message queues can be set up for B and C. QUEUEĪ message queue receives messages from an application and makes them available to one or more other applications in a first-in-first-out (FIFO) manner. There has been some blurring of the lines between these two concepts, as some products now support features that previously belonged only to one or the other category (for instance Azure Service Bus supports both approaches). If you think of the classic Windows message pump, this indeed is more the pull model you describe, but it is really more intra-app than inter-app or inter-box. However the phrase message-queue is also used for internal intra-thread message pumps and the like, and in this context, the usage is indeed different. Both mediate the interactions between various systems. Both can be set to interrupt as well as polling for new messages. Tibco by contrast was (sold as a) messaging backbone, where you could have multiple publishers and subscribers on the same topics.īoth however (and newer competing products) can play in each other's space these days. MQ was originally a 1:1 system, indeed a queue to decouple various systems. QUEUE is indeed somewhat a legacy concept, most recently stemming from systems like IBM MQ and Tibco Rendezvous. By and large, when it comes to vendor software products, they are used interchangeably, and do not have the strong distinctions in terms of push or pull as you describe.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |