0 views collected around this technical thread.
This article explains how distributed applications handle failures through business compensation mechanisms, detailing rollback and retry strategies, consistency models like ACID and BASE, and practical design considerations for microservice architectures.
This article explains why timeouts are inevitable in distributed systems, illustrates the challenges they create, and presents five practical strategies—including using defaults, safe retries, status checks, and user‑focused fallback—to manage slow or failed API calls in microservice architectures.
iQIYI boosted its mobile app’s network request success rate to 99.7% by implementing detailed monitoring, layered retry strategies, optimized timeouts, reduced concurrency, smarter compression, IPv4 preference, TLS 1.3, and connection‑racing techniques, and now targets 99.9% using multipath, QUIC and intelligent traffic scheduling.