0 views collected around this technical thread.
This article details a complete system refactoring project, describing the original monolithic bottlenecks, the design of a distributed architecture, database model reconstruction, phased migration, testing, and rollout strategies to achieve scalable, reliable backend services.
To meet four‑nine stability while unifying divergent on‑premise and public‑cloud login services, the team refactored the hybrid‑cloud account system by consolidating codebases, standardizing DAO layers, deploying gray releases across three active‑active sites, cutting development time by half, latency by 31 %, and technical debt.
This article details a comprehensive system refactoring project that transformed a monolithic, all‑in‑one architecture into a distributed, micro‑service‑based design with a completely rebuilt database model, covering problem analysis, solution design, phased implementation, testing, and rollout strategies.
The article demonstrates how combining Domain‑Driven Design with architecture mapping can transform a complex video‑membership platform by modeling domains, refactoring monolithic components into a clean micro‑service architecture, and quantitatively evaluating the resulting reductions in code size, latency, cost, and improved modularity.
This presentation details Qunar.com's journey from a monolithic system to a service‑oriented, platform‑based architecture, emphasizing domain‑driven design principles, architectural evolution paths, reconstruction strategies, the adoption of the COLA framework, and the resulting improvements in organization and development efficiency.
This article presents a comprehensive case study of the SPA system used by Qunar, detailing its business and technical complexity, the adoption of Domain‑Driven Design and an adapter‑based architecture, the migration to Spring WebFlux for reactive asynchronous processing, and the measurable improvements achieved after refactoring.
The article explores the challenges and motivations behind large‑scale system refactoring, covering stability, coding standards, business rule changes, meeting structures, requirement juggling, technology selection, service division, migration, and implementation strategies, while emphasizing the need for strong team coordination and strategic trade‑offs.
This case study details how Qunar’s hotel pricing platform was reorganized in 2021 using Domain‑Driven Design and explicit architecture principles to streamline cross‑team collaboration, reduce data‑flow complexity, and improve response time by 25%, while aligning system structure with Conway’s Law.
This article details the implementation of Spring StateMachine for refactoring a content platform question bank system, addressing complex state management and coupling issues through state machine patterns.
This article describes how a hotel pricing platform was refactored using Domain-Driven Design, detailing the strategic, tactical, and implementation phases that clarified domain boundaries, introduced a layered architecture, standardized processes, and delivered faster development, better maintainability, and improved operational visibility.
This article describes how Ctrip's vacation product system was modernized by migrating from a legacy .NET/SQL Server architecture to a MySQL‑based, front‑end/back‑end separated platform, detailing the challenges, step‑by‑step storage reconstruction, replication elimination, data model splitting, messaging replacement, and overall architectural improvements.
This article details the architectural evolution and comprehensive refactoring of Tencent's CKV distributed in-memory key-value storage system, highlighting its transition to a two-tier single-process multi-threaded model, multi-tenant resource isolation, deep Redis protocol compatibility, and optimized memory engine, which collectively deliver significant improvements in performance, scalability, and operational cost efficiency.
The article shares practical insights on planning, designing, developing, testing, and rolling out a large‑scale backend system refactor, emphasizing resource limits, pain points of legacy code, unit‑test protection, layering, decoupling, monitoring, and staged deployment to ensure stability during high‑traffic events.
To effectively refactor a legacy system, the article proposes a staged implementation approach that prioritizes issues by severity, categorizes problems, and tackles easier tasks first, thereby concentrating limited resources, reducing risk, and delivering visible improvements in usability, performance, and scalability across successive phases.