This guide explains PHP’s array_flip() function, showing its syntax, parameters, return values, example usage, handling of duplicate values, and important caveats for reliable key‑value reversal.
This article explains the three message delivery semantics, the common causes of duplicate messages in queue systems, and presents concrete producer‑side, broker‑side, and consumer‑side deduplication techniques for Kafka and Pulsar, including code samples and best‑practice recommendations.
Message queues can deliver duplicates under at‑least‑once semantics, so to protect idempotent business logic such as orders and payments you should combine producer‑side idempotence (e.g., Kafka’s enable.idempotence), broker‑side deduplication (e.g., Pulsar), and a consumer‑side guard using unique IDs stored in a database or Redis.
This article analyzes the root causes of message loss and duplication in modern message queues, explains how synchronous and asynchronous sending affect reliability, compares storage strategies like sync‑flush and broker clustering, and offers concrete idempotent handling techniques using database constraints and Redis.
This article explains why message queues are used to decouple services, enable asynchronous processing, smooth traffic spikes, and improve performance, while also detailing the new challenges they introduce such as reduced availability, increased complexity, duplicate consumption, data consistency, message loss, ordering, and backlog, along with practical solutions for each issue.
This article explains several MySQL techniques—INSERT IGNORE, ON DUPLICATE KEY UPDATE, INSERT…SELECT WHERE NOT EXISTS, and REPLACE—plus a practical MyBatis batch‑insert example, to handle large‑scale data imports while preventing duplicate records.
This article explains how to detect and prevent message loss, guarantee reliable delivery across production, storage, and consumption stages, handle duplicate messages with idempotent designs, resolve message backlogs, and implement distributed transactions using transactional messages in systems like Kafka, RocketMQ, and RabbitMQ.
This article shares Qunar's practical experiences with message-driven architecture, detailing consumer handling of duplicate messages, ordering, concurrency control, asynchronous processing, and batch strategies, and presents concrete solutions such as idempotent checks, deduplication tables, versioning, and QMQ's built‑in executors.
