0 views collected around this technical thread.
This article shares hard‑won lessons from production incidents and provides practical guidelines—graceful shutdown, proper startup timing, suitable business scenarios, reliability patterns, and idempotent handling—to use Spring Event safely and effectively in Java backend systems.
This article explains the Observer and Publish‑Subscribe design patterns, compares their concepts and implementations, and provides ten practical Python code examples ranging from simple event notification to distributed messaging with libraries such as pubsub, redis, asyncio, Flask, threading, ZeroMQ, and PySide2.
This article explains the concepts, differences, and implementation approaches of the Observer and Publish‑Subscribe design patterns, and provides ten practical Python code examples covering GUI, networking, asynchronous, and distributed scenarios.
MQTT is a lightweight, publish/subscribe messaging protocol ideal for IoT and mobile environments, offering low bandwidth usage, reliability, and TLS/SSL security, and the article provides a detailed PHP example demonstrating connection, subscription, publishing, message processing, and graceful disconnection.
This article explains how to design and implement a basic task system—covering task configuration, display, progress tracking, and reward collection—while using Kafka for decoupling services and a publish/subscribe event layer to keep task logic independent of event sources.
This article explains the Observer (publish‑subscribe) pattern, illustrates it with a humorous dialogue, provides complete Go interface and struct implementations for subjects and observers, shows sample client code and output, and discusses practical refactoring using the pattern for configuration changes.
This article explains the Observer pattern, compares it with the Publish‑Subscribe model, showcases Java's built‑in Observable and Observer classes, provides complete code examples, and discusses practical considerations such as memory leaks and performance optimizations.
This article explains how MQTT handles message publishing and subscribing, covering topic structures, QoS levels, retain flags, payload details, duplicate fields, subscription formats, packet identifiers, subscription acknowledgments, and unsubscribe procedures, providing a comprehensive overview of the protocol's messaging workflow.
MQTT and CoAP are lightweight IoT communication protocols with distinct architectures—MQTT uses a publish/subscribe model ideal for WAN scenarios and bandwidth‑constrained devices, while CoAP follows a request/response pattern suited for local networks and HTTP compatibility, and the article explains their differences and appropriate use cases.
This article explains how modern message middleware works by describing the two primary communication styles—message queuing and publish‑subscribe—illustrating each with examples, comparing their characteristics, and listing common middleware products to help developers choose the appropriate solution for their backend systems.
This article explains the motivations behind using message‑queue middleware, outlines its benefits such as decoupling, asynchronous processing and peak‑shaving, describes point‑to‑point and publish‑subscribe communication models, and provides a detailed overview of Kafka’s architecture, terminology, data flow, storage strategy, and consumer group mechanics.
MQTT is a lightweight, open‑source publish/subscribe protocol that powers the IoT’s global nervous system by delivering small‑header messages over TCP/IP with configurable QoS, low bandwidth, and optional TLS security, making it ideal for battery‑constrained devices, scalable deployments, and real‑time applications such as home monitoring.
This article introduces the MQTT protocol, outlines its key characteristics, explains the challenges it poses for IoT messaging, and details how JMQ addresses these challenges through a layered proxy‑broker architecture, subscription management, quality‑of‑service handling, and real‑world JD deployment.
This article explains how EventBus replaces explicit publisher‑subscriber registration for in‑process event dispatch in Java, provides a concise code example, a one‑minute migration guide, details on listeners and producers, a terminology table, and a comprehensive FAQ covering usage, design decisions, and testing considerations.