This article explains the fundamentals of Remote Procedure Call (RPC), covering its definition, architectural components, communication protocols, serialization process, complete call workflow, and the main technologies and frameworks used in modern backend systems.
This article examines the shortcomings of decentralized and micro‑service‑only approaches for enterprise integration, argues for version‑less services, explains how a centralized ESB and multi‑center architecture can balance security, efficiency, and scalability, and outlines practical design patterns and component roles.
This article explains how to design and deploy a fault‑tolerant Redis architecture using master‑slave replication, multiple Sentinel instances, and a virtual IP so that the service remains available despite process crashes, server outages, or network partitions.
To tackle Meituan‑Dianping’s massive POI and user data challenges, the team built a hybrid 3NF‑plus‑dimensional data warehouse with ODS, BAS, FACT, and optional TOPIC layers, added Kylin‑based pre‑computation cubes, a plug‑in middle‑platform service (metric dictionary, rule engine, compute engine), and interactive ECharts visualizations, delivering unified metrics, faster ad‑hoc queries, scalable analytics, and reduced development costs.
This article outlines the progressive stages of system architecture—from a single‑server LAMP setup through application‑data separation, caching, clustering, read/write splitting, CDN, distributed storage, NoSQL, business decomposition, and finally distributed services—while detailing essential technologies such as message queues, service frameworks, service buses, communication patterns, and governance mechanisms like Dubbo and OSB.
This article explains how to transform a classic layered monolithic architecture into microservices using Domain‑Driven Design, illustrates real‑world cases from Alibaba Cloud's EDAS platform, and shares practical best‑practice guidance on development, deployment, networking, and common microservice patterns.
This article explains how to split a classic layered architecture into microservices using Domain‑Driven Design, shares real‑world HSF/EDAS case studies, discusses deployment, operation, performance, and common microservice patterns, and offers practical best‑practice recommendations.
This article explores the design of distributed service frameworks, detailing Dubbo’s architecture—including RPC foundation, service publishing, call chains, registry, governance, protocol support, module layers, and the step-by-step processes for exposing and consuming services—providing a comprehensive guide for backend developers.
This article details how New Dada transformed its financial account system from a simple courier‑focused service into a platformized, standardized solution that serves multiple business entities, improves automation, and enhances development efficiency through unified APIs and self‑service tools.
Meituan’s group‑buy order system was refactored from a monolithic, single‑point‑failure design into a sharded, micro‑service architecture with connection‑pool middleware, dual‑cluster databases, and robust messaging, delivering stable, high‑performance handling of millions of daily orders even during peak events.
This article recounts Mogujie's journey from a small PHP‑based LNMP stack to a Java‑driven micro‑service architecture, detailing the operational challenges, standardization efforts, continuous integration pipeline, and full‑link tracing techniques that enabled scalable, reliable e‑commerce services.
This article breaks down Dubbo’s distributed service framework, detailing its RPC foundation, service publishing and consumption, call chain, registry and governance, system roles, protocol choices, layer-by-layer architecture, and the step-by-step processes of exposing and consuming services.
This article explains the fundamentals of Service‑Oriented Architecture, detailing what services are, their key characteristics, common challenges like consistency and security, and how enterprise service bus patterns such as Broker and Message Bus enable scalable, loosely‑coupled integration.
Facing over 140 million monthly active users, Weibo evolved from a LAMP stack to a sophisticated third‑generation architecture that separates interface, service, and resource layers horizontally and adds vertical dimensions of business, technology, monitoring, and governance, leveraging Java, SOA, custom RPC, message queues, SSD caching, and a distributed tracing system to ensure high availability and performance.
The article details how Weibo’s cache infrastructure progressed from simple Memcache deployments to a sophisticated, service‑oriented architecture featuring multi‑layer caching, proxy layers, dynamic configuration, monitoring, and automated scaling to meet massive read‑write demands and high availability requirements.
The article details how Mogujie's e‑commerce transaction system evolved from a monolithic PHP application to a service‑oriented architecture through DB vertical sharding, service decomposition, custom sharding component TSharding, and performance optimizations such as asynchronous processing, caching, and distributed transaction handling to support rapid growth and high‑availability requirements.
This article details Uber's transition to a modular microservice architecture, the RFC process for new services, and the design, implementation, and operational lessons learned from creating Tincup, a high‑performance currency and exchange‑rate service supporting dozens of currencies worldwide.
This article details Uber's transition to a modular microservice architecture, describing the RFC process for new services, the design and implementation of the Tincup currency service, and the technologies—such as MVCS, UDR, Tornado, TChannel, and Thrift—used to ensure scalability, reliability, and efficient production deployment.
This article describes the reconstruction of an order‑reservation‑refund system, detailing business background, abstraction of reservation flows, layered business classification, validation stack implementation, unified data models, mechanism‑strategy separation, and step‑by‑step deployment practices for a robust backend service.
This article explains Dubbo’s ten‑layer architecture, detailing each layer’s responsibilities, the service definition, registration, monitoring, communication protocols, and the package structure that together enable a flexible, decoupled distributed RPC system for backend development.
This article introduces the key OpenStack services—Nova, Neutron, Keystone, Glance, Horizon, Cinder, Swift, Heat, and Ceilometer—explaining each component’s role, functionality, and how they collectively enable scalable compute, networking, identity, image, dashboard, block storage, object storage, orchestration, and telemetry in cloud environments.
The article explores the multiple demands on internet systems, explains why business service granularity is the biggest obstacle to microservice adoption, and shares practical insights on designing a cloud‑native platform with Docker, Kubernetes, unified monitoring, API governance, and multi‑tenant resource isolation.
This article outlines Sogou's infrastructure evolution under rapid business iteration, detailing stages of compute and storage horizontal scaling, serviceization, and stream computing, while sharing the practices, principles, lessons learned, and reflections that guided the platform's architectural transformation.
The article recounts ChuYe's evolution from a monolithic setup to a clustered micro‑service architecture, detailing the challenges of debugging, deployment, and monitoring, and describing the solutions implemented—including service clustering, automated deployment platforms, Docker usage, and comprehensive logging and audit systems—to improve agility and operational efficiency.
The article explains 58.com’s service‑oriented architecture that combines dual‑master MySQL replication, a standby database, and Redis caching to provide high‑availability read/write operations, outlines their scaling process, and details a four‑step cache‑consistency strategy.
During Double 11, JD.com’s product detail page handled tens of billions of requests without downtime by introducing a unified service architecture that consolidates promotion, inventory, recommendation, and other functions behind a single Nginx+Lua entry point, employing multi‑level caching, service isolation, and flexible degradation mechanisms.
This article describes JD’s unified service architecture for the product detail page that handled tens of billions of requests during Double Eleven, detailing the multi‑level caching strategy, Nginx+Lua access layer, service isolation, degradation mechanisms, and front‑end logic offloading.
This article explains how Vipshop’s flash‑sale platform handles massive traffic spikes by redesigning system modules, adopting service‑oriented architecture, implementing async processing, multi‑stage caching, database optimizations, and comprehensive monitoring to ensure stability and scalability.
The article analyzes the practical differences and overlaps between RESTful APIs and Service‑Oriented Architecture, offering guidance on when to build services versus APIs, outlining each approach’s focus, best practices, and a step‑by‑step method for creating RESTful APIs within a unified strategy.
This article describes how a legacy .NET contract management system was transformed into a set of independent microservices using a strategic decoupling approach, explains microservice fundamentals and advantages, and introduces the Ruby‑based Stencil framework with code generation, CI templates, and one‑click AWS deployment to accelerate development and operations.
The article examines the evolution from traditional SOA and ESB to modern microservices, outlining key characteristics such as componentization via services, business‑aligned team structures, treating services as products, lightweight communication, decentralization, automation, failure‑tolerance, and evolutionary design, while discussing practical adoption challenges.
