IBM MQ -> RabbitMQ -> Kafka -> Pulsar
š—œš—•š—  š— š—¤ IBM MQ was launched in 1993. It was renamed to WebSphere MQ in 2002 and to IBM MQ in 2014. IBM MQ is a widely successful product, used extensively in the financial sector.
š—„š—®š—Æš—Æš—¶š˜š— š—¤ RabbitMQ's architecture differs from IBM MQ and more closely resembles Kafka. Producers publish messages to exchanges with specified exchange types like direct, topic, or fanout. Exchanges then route and deliver messages to queues based on predefined bindings and rules. Consumers subscribe to queues and receive messages routed to them by the exchanges.
š—žš—®š—³š—øš—® In 2011, LinkedIn open-sourced Kafka, a distributed event streaming platform. Kafka optimizes for write throughput and handles real-time data feeds with low latency. Its unified event log enables event streaming. Its simplicity and fault tolerance have allowed it to replace products like AMQP-based queues.
š—£š˜‚š—¹š˜€š—®š—æ Originally developed by Yahoo, Pulsar is an all-in-one messaging and streaming platform. Its cloud-native architecture enables better cluster scaling and partition migration. Pulsar uses a two-layer architecture with a serving layer and persistent layer. It natively supports tiered storage, leveraging cheaper object storage like AWS S3 for long-term persistence.
Which message queues have you used?