Thank you all.
This article examines how AI‑assisted coding tools combined with a domain‑driven, spec‑driven workflow (DDD‑SDD) can reshape backend development from ad‑hoc “vibe coding” to a disciplined, automated production pipeline, illustrated with a real‑world retail feature implementation.
This article recounts a frontend team's six‑month evolution with AI coding tools—from initial trial and error to systematic prompt engineering, case‑study implementations, and a disciplined workflow that turns AI into a controllable productivity partner while preserving core engineering skills.
This article describes how a company transformed its fragmented product systems into a unified, domain‑driven middle platform that supports multiple industries, detailing the architectural philosophy, modular design, service layering, template‑based modeling, and the reverse empowerment of legacy restaurant services.
This article explains how a unified, maintainable vector icon library was designed, built, and deployed across multiple platforms—including web, mini‑programs, and native apps—using SVG, font formats, Iconify, and automated CI/CD pipelines to boost design‑development collaboration and product consistency.
This article details the step‑by‑step architectural evolution that merged retail and catering product systems into a shared, extensible platform using domain‑driven design, service standardization, and incremental vertical and horizontal upgrades to reduce technical debt and improve scalability.
This article examines the challenges of a legacy MVC‑based retail product system, explains why a shift to Domain‑Driven Design improves flexibility and scalability, and outlines concrete architectural and data‑model optimizations for robust backend development.
This article explains APISIX’s multi‑process architecture and request lifecycle, then explores various ways to develop external plugins—including SideCar‑based plugins, WASM modules, and LuaJIT FFI—detailing their implementation steps, advantages, and limitations to help developers choose the optimal approach for extending the cloud‑native gateway.
This article examines the challenges of a tightly coupled retail product system and proposes a domain‑driven, micro‑service architecture that decouples business units, introduces unified domain models, and enables flexible, scalable solutions for both retail and catering operations.
This article examines the challenges of test data generation in fast‑moving software projects and presents a self‑developed Test Data Management solution that balances efficiency, usability, security, quality, generality, and cost through adaptive concurrency control, masking policies, and a multi‑master architecture.
This article explores the challenges of retail product systems and presents a domain‑driven design approach, detailing the “Dao” (strategic planning) and “Shu” (technical tactics) of architecture, the divide‑and‑conquer plus orchestration strategy, abstract domain models, layered DDD structure, and data flow management to achieve a flexible, resilient solution.
