Backend Architecture and Stability for Xianyu Local Services

The document outlines the technical background and challenges of Xianyu's local services, focusing on the "idle time" (part‑time) and "idle space" (rental) scenarios that involve third‑party suppliers.

Key problems include rapid supplier onboarding, heterogeneous supply quality, and maintaining service stability. The proposed solution reuses core platform capabilities (user, product, transaction) and defines three domains: merchant, audit, and independent business.

Architecture emphasizes flow control (high‑concurrency rate limiting with Sentinel), monitoring (exception alerts), and data safety (idempotent retries). Data reconciliation uses a status‑change log table (NoSQL) and a business product table (distributed lock + unique key) to guarantee consistency.

Exception handling is unified via a generic LocalBizException wrapper, allowing suppliers to receive error codes and messages without custom catch blocks. A timed reporting mechanism aggregates hourly status changes (e.g., listings, delistings, audit failures) and pushes summaries to DingTalk.

Open APIs expose product audit queries and operation‑log verification. Stability measures include rate‑limit alerts, prolonged failure detection, and automatic message discarding after retry thresholds, with optional manual investigation.

The summary highlights a dynamic response mechanism, robust stability governance, and future directions toward abstracting common patterns across expanding independent business domains.