Billions and Billions Served: Real-Time Distributed Messaging
Dissecting Message Queues: Tyler Treat at Brave New Geek reports an analysis of several different message queues and describes the differences in throughput and message latency between brokered systems (such as NSQ) and brokerless systems (such as ZeroMQ). Graphs of his results may provide information about which type of system is best for different contexts and needs.
NSQ: A Realtime Distributed Messaging Platform: Bitly developers Matt Reiferson and Jehiah Czebotar have designed NSQ to “operate at scale, handling billions of messages per day.” It serves as the backbone of an infrastructure composed of loosely connected services running on many computers. With no single point of failure, it has high availability, reliability, and fault tolerance. For use with any data format, NSQ is easy to configure and deploy.
The Fun of Experimenting with a More Advanced Microservice Application – Building a Slack “Done This” Tracker: Ad Van der Veer at Giant Swarm explains how he used NSQ as one of three components of a method to manage complexity in the architecture layer of a microservice setup.
Reliable, Low-Latency Request-Reply with ZeroMQ: Steve Donnelly at AddThis describes the need for a reliable, low-latency messaging library on a website whose tools are loaded more than 3 billion times and explains how this a cross-platform, cross-language library works.
dev.life – Interview with Salvatore Sanfilippo: Gareth Wilson at Fog Creek Software interviews Salvatore Sanfilippo, the creator of Redis at Pivotal, who is working on a new open-source project for a distributed message queue.