Tagged articles
service-oriented
27 articles · Page 1 of 1
Microservices, also known as microservice architecture, is a cloud‑native approach that breaks a single application into loosely coupled, independently deployable services, each with its own tech stack, communicating via REST APIs, event streams, or message brokers, and organized around business capabilities and bounded contexts.
architecturecloud-nativedistributed systems
0 likes · 3 min read

This article chronicles the five‑year architectural evolution of the Vivo official e‑commerce platform, detailing its transition from a PHP‑based monolith to a service‑oriented, micro‑service ecosystem with independent subsystems and global‑ready internationalization, while sharing practical lessons and design decisions.
e-commerceinternationalizationmicroservices
0 likes · 14 min read

This article provides a comprehensive technical guide on building large‑scale distributed websites, covering characteristics, architectural goals, patterns, performance, high‑availability, scalability, extensibility, security, agility, and a detailed e‑commerce case study with practical diagrams and capacity estimations.
CachingHigh Availabilitydistributed systems
0 likes · 26 min read


ITPUBJan 21, 2022 · Backend Development
This article explains how to design and evolve a high‑concurrency server architecture for e‑commerce applications, covering load balancing, database clustering, NoSQL caching, CDN static assets, message‑queue based asynchronous processing, tiered caching, service‑oriented decomposition, redundancy, and automation to ensure reliable performance under massive traffic spikes.
Cachingclusteringhigh concurrency
0 likes · 21 min read

This article provides a comprehensive technical overview of large‑scale distributed website architecture, covering characteristics, goals, common patterns, high‑performance and high‑availability designs, scalability, extensibility, security, agility, a seven‑layer reference model, and a detailed e‑commerce case study with practical optimization steps.
CachingHigh Availabilitydistributed systems
0 likes · 26 min read

The article explores the fundamental concepts of software architecture, illustrating how massive platforms like Weibo handle millions of users through layered design, service decomposition, multi‑level caching, distributed tracing, and capacity planning to achieve high scalability and reliability.
Backendarchitecturedistributed systems
0 likes · 21 min read

This article explains Uber's Domain‑Oriented Microservice Architecture (DOMA), describing why microservices were adopted, how DOMA structures domains, layers, gateways and extensions, the benefits observed, and practical advice for companies of different sizes considering a similar evolution.
Ubermicroservicesscalability
0 likes · 19 min read

This article explores the fundamentals of monolithic and microservice architectures, assesses the benefits, costs, and risks of adopting microservices, and provides practical criteria—including business complexity, team size, and technical readiness—to help decide the optimal moment for migration.
Backendcloud-nativeevaluation
0 likes · 16 min read

Beike’s real‑estate platform transitioned from a monolithic application to a service‑oriented, domain‑driven mid‑platform, detailing the architectural analysis, phased evolution, componentization, data services, and operational insights that enabled scalable, reusable business capabilities across multiple city‑level services.
R&D managementarchitecturecase study
0 likes · 15 min read

System refactoring succeeds when the Dao—clear, measurable goals and incremental, risk‑controlled planning—guides the Shu of concrete techniques such as service‑oriented design, judicious caching, asynchronous processing, and sharding, while evaluating performance, availability, scalability, elasticity, security, and operability to balance trade‑offs.
architectureperformanceservice-oriented
0 likes · 13 min read

This article explains the distinction between software design and architecture, outlines core principles for building service‑oriented systems, provides a step‑by‑step method for creating new services, and shares practical strategies for refactoring and migrating legacy code without creating future technical debt.
Design PrinciplesNBF frameworklegacy code
0 likes · 8 min read


58 TechFeb 26, 2019 · Backend Development
The article details the step‑by‑step evolution of the WeChat‑like instant messaging platform at 58 Group, describing how the system transitioned from a simple PHP short‑connection architecture to a layered micro‑service architecture using Java‑based RPC, Go‑based short‑connection services, distributed storage, message queues, and clear separation of storage, logic, and interface layers.
Gobackend architecturedistributed storage
0 likes · 12 min read

Backend performance can be significantly improved through six key strategies—caching, hardware upgrades, business‑logic optimization, service‑oriented architecture, asynchronous processing, and leveraging search engines—each explained with practical considerations and real‑world examples to enhance system throughput and reliability.
asynchronousoptimizationservice-oriented
0 likes · 4 min read


JD TechApr 28, 2018 · Backend Development
The article chronicles JD.com's product system evolution—from early SQL Server replication bottlenecks, through Redis‑based read services and full service‑oriented redesign with MySQL clustering, to a decoupled, multi‑layered platform that achieves high availability, scalability, and operational efficiency for billions of SKUs.
Backende-commercescalability
0 likes · 12 min read

This article examines VIPshop's evolution from a simple LAMP‑based outlet site to a multi‑layered, service‑oriented e‑commerce platform, detailing its business model shifts, architectural milestones, key design principles, and governance strategies for building a flexible, high‑availability operation system.
Platform Designe-commerceservice-oriented
0 likes · 13 min read


21CTONov 25, 2017 · Backend Development
This article traces the evolution of application architectures—from vertical monolithic designs through RPC and SOA to modern microservices—explaining the motivations, key characteristics, deployment patterns, and trade‑offs of each approach for scalable, maintainable backend systems.
Backendservice-orientedsoftware design
0 likes · 7 min read

This article outlines a comprehensive approach to building high‑concurrency web systems by introducing layered architecture, modular segmentation, distributed deployment, server clustering, asynchronous processing with message queues, caching strategies, service‑oriented design, and automated redundancy to achieve high availability and scalability.
Asynchronous Processingbackend architecturehigh concurrency
0 likes · 12 min read

The article examines common misconceptions about game server performance, outlines essential message pipelines, introduces Gate as a reverse‑proxy for low‑latency scene synchronization, discusses integrating a message‑queue (MQ) for decoupled services, and presents a service‑oriented RPC framework with patterns to build maintainable, scalable multiplayer back‑ends.
GateMessage QueueNetworking
0 likes · 34 min read

This article examines VIPshop’s business model evolution and the technical transformation of its e‑commerce platform, detailing the shift from a single‑application LAMP monolith through vertical and distributed architectures to a cloud‑native, service‑oriented design, and outlines the key governance, scalability and operational challenges addressed along the way.
Platform Designcloud-nativee-commerce
0 likes · 14 min read

The article chronicles LinkedIn’s journey from a single‑server Leo monolith to a highly distributed, service‑oriented backend architecture, detailing the introduction of member graphs, read‑only replicas, caching layers, Kafka pipelines, Rest.li APIs, super‑blocks, and multi‑data‑center deployments to support billions of daily requests.
KafkaLinkedInRest.li
0 likes · 9 min read


21CTOFeb 24, 2016 · Backend Development
This article presents a comprehensive e‑commerce website architecture case study, detailing functional and non‑functional requirements, initial single‑server design, capacity estimation, and progressive evolution toward a distributed, high‑availability architecture with clustering, caching, load balancing, service‑orientation, and database sharding.
Cachingarchitecturedistributed systems
0 likes · 14 min read


21CTOJan 25, 2016 · Backend Development
The article shares a veteran engineer’s fourteen‑year journey from a simple personal homepage to a billion‑page‑view e‑commerce platform, outlining essential principles, knowledge structures, design philosophies, infrastructure choices, and operational practices needed to build and maintain large‑scale web systems.
backend developmentperformance optimizationscalable systems
0 likes · 31 min read

The article examines how 1号店 evolved from a simple MVC architecture to a service‑oriented backend, emphasizing a comprehensive logging system that enables precise error classification, rapid issue localization, and proactive monitoring, ultimately improving reliability and scalability.
Loggingbackend architecturemonitoring
0 likes · 4 min read

The article chronicles how 58.com’s web architecture evolved from a tiny, single‑machine setup to a multi‑layer, Java‑based, highly available service‑oriented platform, detailing the technical decisions, scaling challenges, and automation practices adopted at each traffic milestone.
High Availabilityarchitecturescalability
0 likes · 14 min read

The article explains microservice architecture as a set of independently deployable services each focused on a single function, illustrating their roles, communication methods, deployment considerations, and key characteristics such as single responsibility, own data storage, and replaceability.
Independent Deploymentmicroservicesreplaceable
0 likes · 14 min read

The article chronicles how 58.com’s website architecture evolved through multiple growth stages—from a tiny single‑machine setup to a distributed, service‑oriented platform—by addressing scaling bottlenecks with technologies such as LAMP, read/write separation, vertical splitting, caching, and automated deployment.
Backendarchitecturehigh-availability
0 likes · 13 min read


21CTOAug 15, 2015 · Backend Development
An in‑depth look at Weibo’s evolution to its third‑generation backend system, detailing the orthogonal decomposition model, three‑tier horizontal layering, key middleware such as MCQ, Motan RPC, SSDCache, and the WatchMan tracing platform that together enable high‑availability, massive concurrency, and low‑latency services for billions of users.
Distributed TracingHigh Availabilitybackend architecture
0 likes · 12 min read
