Tagged articles
message deduplication
14 articles · Page 1 of 1
The article explains that idempotency prevents the same operation from being executed twice, illustrates a real double‑charge bug, evaluates five concrete approaches—including Redis check‑then‑set, DB unique index, optimistic lock, Redis distributed lock, and a message deduplication table—details their failure conditions and suitable scenarios, and recommends combining Redis lock with a database unique index for the most robust protection.
Distributed LockIdempotencyOptimistic Lock
0 likes · 10 min read

This article explains practical strategies to avoid duplicate message consumption in Kafka, covering business idempotency with unique IDs, database or Redis deduplication tables, enabling producer idempotence, consumer-side checks, and Kafka's transaction-based exactly‑once semantics, along with their trade‑offs and suitable scenarios.
BackendIdempotencyKafka
0 likes · 4 min read

This article presents a comprehensive, end‑to‑end solution for preventing duplicate consumption in RabbitMQ by combining architecture design, routing strategies, idempotent controls, state machines, and ACK mechanisms, and details six concrete implementation options with code examples.
IdempotencyJavaRabbitMQ
0 likes · 9 min read

Kafka ensures that a producer’s repeated message sends, caused by network glitches or broker failures, result in only one persisted record per partition by using a unique Producer ID, monotonically increasing sequence numbers, and broker-side tracking of the latest committed sequence for each PID‑partition pair.
BackendKafkamessage deduplication
0 likes · 5 min read

RabbitMQ often suffers from duplicate message consumption due to network glitches, node failures, or ACK issues, but you can eliminate repeats by implementing idempotent processing, using caches or deduplication tables, and leveraging manual acknowledgments or the Message Deduplication plugin, as illustrated with Java examples.
JavaManual AcknowledgmentRabbitMQ
0 likes · 6 min read

This article explains why RocketMQ guarantees at‑least‑once delivery, describes the three typical duplicate‑message scenarios, compares transaction‑based and non‑transactional deduplication approaches (including a Redis‑based solution), provides sample SQL and Java code, and discusses the limitations and best‑practice recommendations for achieving idempotent message consumption.
IdempotencyJavaRocketMQ
0 likes · 20 min read

This article explains why message middleware guarantees at‑least‑once delivery, the problems caused by duplicate consumption, and presents both transaction‑based and non‑transactional deduplication solutions—including a Redis‑backed idempotent table—to achieve exactly‑once semantics in RocketMQ.
IdempotenceRocketMQdistributed systems
0 likes · 19 min read

This article analyzes the at‑least‑once guarantee of message middleware, explains why duplicate deliveries occur, compares simple database‑based deduplication methods, explores concurrency challenges, and presents a non‑transactional, status‑driven idempotence solution using MySQL or Redis with practical code examples and limitations.
IdempotenceMySQLRocketMQ
0 likes · 19 min read

This article explains why message middleware guarantees at‑least‑once delivery, describes three common duplication scenarios in RocketMQ, and presents both transactional and non‑transactional deduplication solutions—including SQL examples and a Redis‑based idempotence library—to achieve exactly‑once processing.
IdempotenceRocketMQdistributed systems
0 likes · 19 min read

Message middleware guarantees at-least-once delivery, but repeated deliveries cause duplicate processing; this article explains RocketMQ's duplicate scenarios, explores simple and advanced deduplication techniques—including database-transactional and Redis-based idempotent tables—and provides practical Java code for implementing exactly-once semantics.
IdempotenceRocketMQdistributed systems
0 likes · 20 min read

This article explains why message middleware guarantees at‑least‑once delivery, the challenges of duplicate consumption, and presents both simple and advanced deduplication strategies—including transactional and non‑transactional approaches using relational databases or Redis—to achieve effectively exactly‑once semantics in RocketMQ.
IdempotenceRocketMQTransactional Messaging
0 likes · 18 min read


21CTONov 10, 2019 · Mobile Development
This article details the design and implementation of a scalable mobile instant‑messaging system for a travel app, covering architecture, data‑channel handling, subscription mechanisms, UI rendering, message de‑duplication, local push strategies, reconnection logic, and future upgrades to WebSocket.
WebSocketdata channelinstant messaging
0 likes · 16 min read

This article explains how to handle high‑concurrency instant‑messaging scenarios by designing message deduplication, optimizing SQLite write performance with batch inserts and WAL mode, improving query speed with indexes and caching, and reducing UI refresh overhead through delayed and scroll‑aware updates.
SQLiteWALinstant messaging
0 likes · 19 min read

This article details the design, architecture, and implementation of a mobile instant‑messaging system for a travel platform, covering data channel design, message subscription, UI rendering, deduplication, local push, reconnection strategies, and the planned migration to WebSocket.
Real-time MessagingWebSocketmessage deduplication
0 likes · 17 min read
