This guide explains what NSQ is, shows how to install NSQ via Docker, set up the PHP‑NSQ extension by installing libevent and the PECL package, and provides complete PHP code examples for publishing, deferred publishing, and subscribing to messages.
This comprehensive guide explains the role of message queues in distributed systems, compares the architectures and core concepts of Kafka, Pulsar, RocketMQ, RabbitMQ, and NSQ, and provides practical criteria for selecting, configuring, and operating a message‑queue solution in high‑performance, high‑availability environments.
This comprehensive guide compares five popular message queue systems—Kafka, Pulsar, RabbitMQ, RocketMQ, and NSQ—covering their architectures, core concepts, selection criteria, feature differences such as ordering, latency, durability, scaling, and operational considerations, to help engineers select the most suitable solution for their use cases.
The article surveys major message‑queue systems—Kafka, Pulsar, RocketMQ, RabbitMQ, and NSQ—detailing their architectures, key features, selection criteria such as ordering, scalability and latency, performance benchmarks, operational considerations, and typical use cases, and advises which platform best fits high‑throughput, reliability, low‑latency, or lightweight Go‑centric scenarios.
This guide compares Kafka, Pulsar, RocketMQ, RabbitMQ, and NSQ across architecture, consumption models, delay and dead‑letter support, persistence, ordering, multi‑tenant isolation, and performance, recommending Kafka for high‑throughput log processing, Pulsar for transactional delayed messaging and disaster recovery, and NSQ for Go‑centric custom solutions.
The article compares the architectures of NSQ (YouZan branch), Kafka, and RocketMQ—detailing their coordination mechanisms, storage models, consistency guarantees, and operational trade‑offs—while recommending Kafka for log‑big‑data workloads, RocketMQ for massive topic counts, and NSQ for extensibility and lightweight deployment.
This article introduces NSQ, an open‑source Go‑based distributed message queue, detailing its core components, scalable high‑availability deployment topology, backup and replay mechanisms, and monitoring practices to ensure reliable, fault‑tolerant message processing.
This article introduces NSQ, an open‑source Go‑based distributed message queue, detailing its high‑performance architecture, core components (nsqd, nsqlookupd, nsqadmin), recommended high‑availability deployment topology, backup and replay mechanisms, and essential monitoring practices for reliable backend operations.
This article explains the design and implementation of NSQ dual‑ and multi‑data‑center architectures using a lookup‑migrate proxy, covering deployment scenarios, routing strategies, migration phases, JSON response transformations, and practical lessons learned for reliable message publishing and consumption across data centers.
This guide explains how to construct a client library for Youzan's customized NSQ, covering workflow configuration, nsqd discovery via nsqlookupd, connection establishment, message publishing and consumption, ordered consumption, and the implementation of message tracing with concrete command syntax and response handling.
This article provides a comprehensive overview of NSQ, covering its core components, message flow, producer and consumer interactions, key configuration parameters, handling of timeouts, backoff mechanisms, service discovery with nsqlookupd, and practical considerations for scaling and reliability.
YouZan’s experience with Flume shows how the at‑least‑once delivery model, combined with FileChannel storage and custom extensions such as an NsqSource, hourly‑based HdfsEventSink, metric reporting server, and timestamp interceptor, can reliably move MySQL binlog data to HDFS, while tuning transaction batch size and channel capacity boosts throughput and stability, paving the way for a unified management platform.
NSQ is a lightweight, high‑performance open‑source message queue written in Go, and this article explains its core components (nsqd, nsqlookupd, nsqadmin, utilities), message flow architecture, configuration details, deployment recommendations, and additional considerations such as persistence, delivery guarantees, and scalability.
This article explains the design of an extended NSQ message format, illustrates its application in load‑testing, service isolation, and channel‑level filtering scenarios, describes the NSQ migration proxy tool and Spark/Flume connectors, and outlines future enhancements such as flow control and batch subscription.
This article explains the design of a real-time customer behavior collection platform that uses NSQ for messaging, Storm for streaming processing, and HBase for storage, covering architecture, data flow, reliability guarantees, and deployment considerations.
