The basic architecture of a message queue is simple, there are client applications called producers that create messages and deliver them to the message queue. An application, called consumer, connects to the queue and retrieves the messages to be processed. Messages are stored in the queue until the consumer retrieves them for processing.In this post I will share some the benefits you can gain from utilizing message queues in your application architecture and look at some of the queuing platforms available today. In the following series of posts I will explore how message queues can be utilized with Sitecore:
- Part 2 – Produce and Consume messages with Sitecore
- Part 3 – Handling failed messages with a deadletter queue and Sitecore Workflow
- Part 4 – Do I really need an external message queue?