1 views collected around this technical thread.
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.
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.
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.
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.
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.
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.
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.
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.
This article explores a real‑world scenario where a support manager faces nightly batch job interruptions, analyzes common database and environment failures, and presents a systematic redesign of the batch framework and executor to enable automatic retry, reducing manual intervention and improving operational reliability.
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.
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.
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.
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.
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.
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.
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.