Message queues : The right way to process and transform realtime messages

This article discusses the differences between pub/sub and queue based messaging patterns and why both are sometimes needed. It explains that a pub/sub pattern is designed so that each message published is received by any number of subscribers, while a queue-based pattern typically requires that each message is received only once by a single subscriber in a linear yet distributed fashion. The article also explores scenarios where the pub/sub pattern works well and when it feels like forcing a square peg into a round hole. It then introduces message queues as the solution to this problem, explaining how they provide a buffer to cope with sudden spikes, ensure data integrity, and can be used in conjunction with Ably's realtime messaging platform for processing real-time data on servers.