Tagged articles

service evolution

2 articles · Page 1 of 1

Sep 7, 2026 · Backend Development

Independent Deployment ≠ Independent Evolution: Designing Dependencies, Routing & Release Architecture

The article explains why independent deployment doesn't guarantee independent service evolution, detailing five required capabilities—identifiable dependencies, compatible interfaces, controllable traffic routing, verifiable releases, and recoverable failures—using a refund service case study to illustrate dependency topology, interface evolution patterns, phased release strategies, and evidence-based rollback decisions.

canary deploymentdependency managementdistributed systems

0 likes · 21 min read

Independent Deployment ≠ Independent Evolution: Designing Dependencies, Routing & Release Architecture

DeWu Technology

Mar 9, 2022 · Backend Development

Evolution of a Message Platform from v1.0 to v3.0

The DeWu App’s messaging platform progressed from a tightly‑coupled v1.0 push API plagued by latency and priority issues to a v2.0 unified interface with fatigue control, multi‑version sending, and robust monitoring, and finally to a v3.0 modular, stateless architecture driven by an orchestration engine that separates core capabilities from business extensions while providing dynamic strategies, SLA‑level latency guarantees, and comprehensive stability monitoring.

message platformmonitoringservice evolution

0 likes · 6 min read

Evolution of a Message Platform from v1.0 to v3.0