Tagged articles
retry mechanism
26 articles · Page 1 of 1
This comprehensive guide covers RocketMQ production operations including cluster deployment with NameServer and Broker configurations, message retry mechanisms with backoff strategies, dead letter queue handling and reprocessing, monitoring with Prometheus alerts, and troubleshooting procedures for common issues like message accumulation, disk full, and broker failures.
Cluster DeploymentDead Letter QueueMessage Queue
0 likes · 67 min read

After scaling a Spring Boot app to three Kubernetes replicas, @Scheduled tasks ran thrice, generating duplicate reports. The author evaluates distributed locks but adopts JobRunr for persistent, retryable, and monitorable background jobs, demonstrating integration with Spring Boot 4, code patterns for fire-and-forget, recurring, and delayed tasks, plus idempotency and deduplication strategies.
Background JobsDistributed Task SchedulingIdempotency
0 likes · 16 min read

Spring Framework 7 introduces @Retryable and @ConcurrencyLimit annotations for method-level retry and concurrency control, enabling developers to handle transient failures and limit parallel executions without third-party libraries, though they operate per-JVM and lack distributed coordination.
@RetryableConcurrencyLimitJava
0 likes · 9 min read

This article presents the local message table pattern as a lightweight, production-ready solution for achieving eventual consistency in microservice architectures, covering database schema design, transactional message persistence, scheduled retry mechanisms, idempotent consumption, and real-world incident resolution compared to heavier alternatives like Seata and TCC.
IdempotencyMessage Queuedatabase design
0 likes · 11 min read

This article examines the common data‑consistency challenges when writing to both a database and a Redis cache, evaluates four write‑order strategies, and presents the most reliable approach—writing to the database first then deleting the cache—along with retry mechanisms using scheduled jobs, message queues, and binlog listeners.
Cache ConsistencyElastic-JobRocketMQ
0 likes · 17 min read

This article explains how River, a Go job‑queue library, implements delayed execution, priority handling, exponential‑backoff retries, batch inserts, monitoring, and best‑practice patterns, and compares it with other queue solutions to help developers build reliable, high‑performance background processing pipelines.
GoRiverbatch processing
0 likes · 14 min read

This article explores a supply‑chain consistency framework that tackles distributed transaction challenges by using eventual consistency, detailing its theoretical models, architecture, core components, async execution, retry mechanisms, and a practical code example for Spring‑Boot applications.
annotationdistributed systemseventual consistency
0 likes · 10 min read

The article explains Google Guava’s RangeMap—a map that links non‑overlapping ranges to values—detailing its core features, typical use cases such as retry mechanisms and tiered pricing, and provides step‑by‑step Java code examples that show insertion, querying, overlapping handling, sub‑range views, and removal.
Google GuavaInterval MappingJava
0 likes · 9 min read

The paper presents a scalable, message‑queue‑driven reward system for Bilibili Live that unifies diverse reward types and distribution scenarios through standardized APIs, layered fast/slow queues, idempotent processing, multi‑stage retries, and comprehensive monitoring to ensure low latency, no over‑issuance, and reliable delivery.
BilibiliHigh AvailabilityIdempotency
0 likes · 16 min read

This article examines the data consistency challenges of writing to both databases and caches, outlines four common double‑write strategies, analyzes their pitfalls—especially under high concurrency—and recommends the optimal approach of writing to the database then deleting the cache, while discussing retry mechanisms, scheduled tasks, message queues, and binlog listeners.
Cachedatabase consistencyhigh concurrency
0 likes · 15 min read

This article explains how to integrate Spring Retry into a Spring Boot project to gracefully handle third‑party API failures, covering annotation‑based retries, asynchronous retries, exception filtering, fallback handling, and an optional Hystrix circuit‑breaker extension for comprehensive fault tolerance.
Circuit BreakerHystrixJava
0 likes · 12 min read

This article outlines typical problems such as unreachable domains, signature errors, token expiration, timeouts, HTTP 500/404 responses, pagination inconsistencies, undocumented field changes, and billing issues, and provides practical troubleshooting and mitigation strategies for backend developers working with third‑party APIs.
API integrationerror handlingretry mechanism
0 likes · 15 min read

This article explains the concepts of pessimistic and optimistic locking, compares their use cases, demonstrates version‑based and CAS implementations, and shows a complete Spring Boot example with retry‑enabled optimistic lock handling using AOP and custom annotations.
JPAJava ConcurrencyOptimistic Lock
0 likes · 12 min read

This article examines a Redis 3.x cluster failure caused by a master‑slave switch, detailing how improper Jedis timeout and retry settings triggered a service avalanche, and provides step‑by‑step analysis of the incident, code paths, and recommended configuration adjustments to prevent recurrence.
JedisService Avalancheconnection timeout
0 likes · 12 min read

This article explains the concept, practical applications, version evolution, and deployment strategy of a virtual phone number service, detailing XB and AXB binding modes, asynchronous retry mechanisms, concurrency handling, and monitoring to ensure reliable integration with third‑party PSTN providers.
AXB modeAsynchronous ProcessingBackend
0 likes · 13 min read

This article walks through RocketMQ 4.9.x’s consumption architecture, explaining the roles of NameServer, Broker, Producer and Consumer, the publish‑subscribe model, storage structures, load‑balancing algorithms, long‑polling, concurrent and ordered consumption, progress persistence, and the built‑in retry mechanism.
ConsumerMessage QueueRocketMQ
0 likes · 28 min read

This article outlines typical problems such as domain inaccessibility, signature errors, token expiration, timeouts, HTTP 500/404 responses, inconsistent documentation, and provides practical debugging and mitigation strategies for developers working with third‑party API integrations.
API integrationBackenderror handling
0 likes · 15 min read

This article examines the various reasons why RocketMQ can deliver the same message to consumers multiple times, covering send‑retry mechanisms, consumer‑side exceptions, offset commit and persistence failures, master‑slave synchronization issues, rebalance events, and long‑processing cleanup, and offers guidance on designing idempotent solutions.
Message QueueRebalanceRocketMQ
0 likes · 15 min read


ITPUBMar 11, 2023 · Databases
This article explains why dual‑write consistency between MongoDB and a relational database is challenging, compares common misconceptions with cache usage, and provides practical patterns—including write ordering, retry mechanisms, and scheduled cleanup—to reliably synchronize core and non‑core data.
Data ConsistencyMongoDBdatabase
0 likes · 12 min read

This article explains how to create a custom @FeignRetry annotation that leverages Spring Retry to provide configurable, per‑method retry policies for Feign client calls, including code examples of the annotation, aspect implementation, and usage patterns.
AOPAnnotationsFeign
0 likes · 6 min read

This article introduces the Spring‑Retry and Guava‑Retry frameworks for Java, explains their dependencies, configuration, policies, and back‑off strategies, demonstrates both XML/annotation and programmatic usage with detailed code samples, and compares their flexibility and suitability for backend applications.
Guava RetryJavaretry mechanism
0 likes · 15 min read

This article explains how to build a reliable delayed message queue using Redis, covering business scenarios, requirements such as persistence and retry, the design of Redis data structures, Lua scripts for atomic operations, and a Go implementation with example code for producing and consuming delayed tasks.
GoLuaMessage Queue
0 likes · 13 min read

This article shares a two‑year journey of using Kafka in a high‑traffic restaurant ordering system, covering why message order matters, how network glitches and partition routing cause failures, and the practical retry, partition‑balancing, and database strategies that finally eliminated backlog and duplication issues.
KafkaPartition Balancingbackend development
0 likes · 19 min read

This article shares a year‑long experience of UI automation at Youzan, covering how to select stable business scenarios, choose Puppeteer with Mocha, implement robust element locating, handle dynamic data via API interception, apply wait and retry mechanisms, capture screenshots, log responses, and integrate tests into CI pipelines for reliable regression testing.
API interceptionCI integrationFrontend Testing
0 likes · 13 min read


58 TechMay 22, 2020 · Backend Development
This article presents a comprehensive distributed retry system that leverages a distributed scheduling mechanism to ensure eventual consistency, reduce manual recovery costs, and provide flexible retry strategies, automatic recovery detection, visual management, rate limiting, and intelligent retry for backend services.
backend developmentfault toleranceintelligent retry
0 likes · 13 min read

The article shares a comprehensive, experience‑driven guide on building fault‑tolerant systems—covering retry mechanisms, dynamic node removal, timeout settings, service degradation, decoupling, and business‑level safeguards—to enable a platform that scales from millions to billions of daily requests without relying on manual fire‑fighting.
Operationsfault toleranceretry mechanism
0 likes · 21 min read
