0 views collected around this technical thread.
This article explores how simplifying the traditional "wash‑cut‑blow" haircut process into a lean "cut‑blow" model reveals broader principles of process reengineering, cost reduction, and customer autonomy that can be applied to many industries.
Distributed systems and microservices are often confused, but this article clarifies five major distinctions in design, scope, service division, deployment, and operational practices, illustrating examples such as distributed databases, caches, and computing frameworks versus business‑oriented, independently deployable microservices using containers and CI/CD pipelines.
This article explains why BFF is needed in modern microservice architectures, describes thin and thick BFF designs, outlines typical inter‑process microservice structures, enumerates common BFF problems, and proposes governance principles to keep BFF focused on front‑end experience and backend orchestration.
This article explains how to build a highly reusable shared order service by clearly defining its boundaries, abstracting its internal data model and interfaces, and handling order status management with both main and sub‑status mechanisms, while avoiding tight coupling with other services.
The article shares a chief architect's experience on combining a large‑scale waterfall approach with agile iterations, detailing microservice and BFF design, team organization aligned with Conway's law, and practical application‑boundary principles for a distributed enterprise system.
The article explains why high availability is essential for backend services, defines its core concepts, and outlines key design principles such as minimizing dependencies, avoiding single points of failure, load balancing, resource isolation, rate limiting, circuit breaking, asynchronous processing, degradation strategies, gray releases, and chaos engineering to build resilient APIs.
This article walks through the complete process of designing a budget‑control platform using Domain‑Driven Design, covering background analysis, strategic and tactical design, domain modeling, service decomposition, interface definition, and technical implementation to illustrate how to build a cohesive, scalable backend service.
This article provides a thorough overview of microservice architecture, covering its definition, history, comparison with monolithic and SOA approaches, key characteristics, design patterns, implementation challenges, communication methods, fault tolerance strategies, and practical considerations for adopting microservices in modern software systems.
This article provides a comprehensive overview of microservice architecture, covering its definition, history, differences from monolithic development, key characteristics, comparison with SOA, practical implementation steps, common design patterns, advantages, disadvantages, and essential considerations for successful adoption.
This article presents a comprehensive traffic verification platform that intercepts, records, stores, replays, and load‑tests online request flows to validate functional correctness and performance before cutting traffic to new order‑processing services, offering detailed design, implementation, and practical usage guidance.
This article presents a comprehensive set of practical microservice design guidelines—including stateless services, front‑back separation, domain‑driven business abstraction, use‑case and entity convergence, high cohesion, low coupling, vertical and horizontal slicing, and team self‑organization—to help architects build scalable, maintainable backend systems.
The article shares practical experiences from evolving a mobile app store backend, comparing three API versioning models, detailing challenges of multi‑version client support, describing a two‑stage migration to compatible versioning, and offering design guidelines for scalable, maintainable service interfaces.
The article recounts how Vivo’s App Store backend evolved from a monolith to a service‑cluster architecture while handling millions of daily users by adopting three API versioning strategies—no version, point‑to‑point, and compatible versioning—and progressively refactoring interfaces and services to maintain backward compatibility and improve stability, performance, and maintainability.
This article shares practical hints on designing microservice‑based business architectures, covering problem definition, measurable goals, logical and process views, autonomy standards, real‑world case studies, and DevOps metrics to improve development speed and quality.
The article details Youzan’s Return Shipping Fee insurance service, explaining its consumer and merchant benefits, end‑to‑end workflow, integrated risk‑control mechanisms, insurance‑product specifications, and a layered technical architecture—business, domain, component, and dependency services built with domain‑driven design—to enable scalable, reusable e‑commerce insurance solutions.
This article explains microservices architecture, contrasting it with monolithic systems, outlines the problems solved by microservices, lists their advantages and disadvantages, presents a practical API example with code, and discusses splitting strategies, design principles, and common migration patterns.
This article presents a comprehensive guide to designing service‑center interfaces and data models, covering the Facade pattern, DTO usage, and eleven practical service design principles such as contract‑first, cohesion, granularity, redundancy elimination, statelessness, naming, and operation design, illustrated with code examples and diagrams.
This article explains the benefits of short URLs, outlines their basic workflow, and details a backend design that uses an incremental issuer, base conversion, persistent storage, caching, batch ID allocation, and distributed issuers to achieve efficient, high‑concurrency short‑URL generation.
This article explains why Medium transitioned from a monolithic Node.js application to a microservice architecture, outlines the three core design principles, shares practical strategies for building and operating services, and warns about common pitfalls such as the microservice syndrome.
The article explains how microservices communicate via RPC or event‑driven approaches, analyzes different coupling types, compares event notification and event sourcing, discusses API‑gateway and service composition, and offers practical guidance on limiting microservice count and using internal microservice design.