Message Queue Architecture Overview

Overview

Environments that have large amounts of data or have many applications integrating into a single resource should use Message Queue (MQ) Architecture. Message Queue Architecture helps distributed systems to communicate using an asynchronous service-to-service configuration where messages are stored in a queue until they are either processed or deleted. This architectural configuration can also help with minimizing the number of API calls that need to be managed by an organization.

MQ Applications: Producers and Consumers

Most applications can be categorized as either producers or consumers. Producers are applications that send data to the MQ server. Consumers are applications that take the messages from the MQ server. Other times, applications can be both where they send a message to the messaging server and retrieve a different message.

Message Queue Servers

Decisions can be set up as a message queue server or be integrated with the following MQ servers: 

• Azure Services (see Azure Service Bus for more information)
• RabbitMQ (see About RabbitMQ Message Services for more information)
• MSMQ (see MSMQ Module for more information)
• IBM MQ (see IBM MQ Message Services for more information)
• Apache Kafka (see Apache Kafka for more information)