From the basics of three‑tier architecture to the challenges of scaling, this article explains why monolithic designs become problematic, how fine‑grained and coarse‑grained microservices address complexity, and offers practical refactoring steps for high‑concurrency systems.
This article explains core microservice concepts—including componentization, modularization, centralized vs. distributed systems, and the architectural principles behind microservices—while comparing them to SOA and highlighting practical distinctions that help developers design loosely‑coupled, reusable services.
The article shares a senior engineer’s perspective on evolving payment system architectures—from a simple monolithic WAR package, through a duplicated “chimney” style, to a fully modular micro‑service platform—highlighting why each generation fits different business stages and how domain‑driven design supports rapid market growth.
This article traces Spring's evolution, explains why Spring Boot was created to simplify configuration and deployment, outlines its core features, testing support, convention‑over‑configuration philosophy, and its relationship with Spring Cloud, providing a comprehensive guide for backend developers.
FinTech firms should replace monolithic systems with microservices because the modular style delivers greater agility, maintainability, scalability, availability, and code reuse—crucial for rapid market demands and regulatory change—while acknowledging migration costs, monitoring complexity, and the need for phased refactoring of legacy assets.
The article warns developers about the dangers of blindly following flashy technologies—such as over‑abstracted patterns, NoSQL hype, endless scalability promises, micro‑services mania, and agile buzzwords—by highlighting real‑world pitfalls and urging thoughtful, purpose‑driven engineering decisions.
This article explains the fundamentals of remote method invocation, compares traditional RMI with modern RPC frameworks, introduces Dubbo's architecture and roles, and provides a step‑by‑step guide to quickly develop, build, and run a complete Dubbo application using API‑centric configuration and multicast registration.
Cloud Foundry is an open‑source PaaS that abstracts cloud, framework, and service choices, offering features such as multi‑cloud deployment, standard frameworks, built‑in services, and a modular, message‑driven architecture composed of Router, Cloud Controller, DEA, Health Manager, Service Broker, and NATS, with flexible deployment options for both private and public clouds.
This article shares the design and implementation of a lightweight, robust, and low‑intrusion monitoring management system for microservice traffic, detailing data collection via client filters, Redis‑based structured storage, alerting, rate‑limiting, degradation, and authorization mechanisms, and discusses performance optimizations and future improvements.
This article describes Ant Financial's decade‑long service‑oriented architecture evolution, the challenges of multi‑language and legacy systems, the evaluation of Istio, Linkerd and Conduit, and the design and deployment of the internally built SOFA Mesh using a Golang sidecar and EdgeSidecar to achieve cloud‑native, high‑availability service mesh capabilities.
The article debunks three prevalent misconceptions—treating a development framework as a substitute for an architect, assuming high concurrency and big‑data challenges are inherently difficult, and believing microservice architecture is a universal solution—by emphasizing the importance of proper design, testing, and realistic evaluation of trade‑offs.
This article explains why banks should adopt blockchain systems, outlines three guiding principles, describes typical integration architectures, examines changes to reconciliation and transaction consistency, and offers practical solutions for identity verification, key management, and high‑availability deployment.
The article summarizes the design principles of reactive microservices, covering isolation, single responsibility, autonomy, private state, asynchronous messaging, service discovery, API management, and security, and explains how these concepts enable scalable, resilient cloud‑native systems.
The article explains how increasing business complexity and throughput demands drive system splitting—horizontal scaling, vertical and business sharding, and database partitioning—and describes the subsequent architectural evolution toward micro‑services, caching, indexing, and asynchronous processing to improve capacity, robustness, and performance.
In this interview, Ant Financial’s middleware leaders Yang Bing and Huang Ting discuss the evolution of the SOFA framework, the adoption of Service Mesh, open‑source strategies, cloud‑native transformation, and practical advice for engineers navigating large‑scale financial technology platforms.
This article explains how to construct a PaaS cloud platform using a microservice architecture, Spring Cloud Netflix components, Docker containers, and supporting services such as a gateway, Eureka registration, Hystrix fault tolerance, and a dynamic configuration center.
This article explains how to construct a PaaS cloud platform using microservice architecture and Docker containers, detailing the roles of Spring Cloud Netflix components such as Zuul, Eureka, Hystrix, and Config Server, and covering gateway routing, service discovery, deployment, fault tolerance, and dynamic configuration.
This article presents a practical, China‑centric microservices reference stack built on Spring Cloud, detailing eleven core components—including Zuul, Eureka, Apollo, Kafka, ELK, and Hystrix—while comparing them with alternatives and offering guidance for architects to avoid common pitfalls and accelerate production‑grade deployments.
This article explains microservices architecture, contrasting it with monolithic systems, outlines its core characteristics, communication patterns, advantages, disadvantages, design considerations, API importance, governance practices, fault‑tolerance strategies, container integration, and real‑world examples such as Netflix and Twitter.
This article explains how container technologies like Docker and Amazon ECS enable the transition from monolithic web applications to scalable microservices architectures by improving development agility, resource isolation, and deployment flexibility across cloud environments.
This article provides a comprehensive guide to planning, developing, testing, and monitoring microservices, recommending a range of open‑source tools for documentation, code review, logging, CI/CD, performance testing, and observability to help developers build reliable, scalable services.
The article outlines how to classify microservice-based systems into interface, web, and task categories, describes their architectural evolution, and provides a step‑by‑step methodology for identifying core (golden) functions and processes, distinguishing strong and weak dependencies, and implementing resilient disaster‑recovery strategies for large‑scale e‑commerce events.
This article applies the thermodynamic concept of entropy to software systems, explaining how entropy increase manifests as technical debt and how deliberate entropy reduction through architectural evolution, micro‑services, DevOps practices, and organizational changes can sustain system vitality and productivity.
The article explores how the concept of entropy from the second law of thermodynamics maps onto software systems and organizations, describing entropy increase and reduction, negative entropy, four governing rules, technical debt, progressive architecture patterns such as the strangler and refactoring approaches, and real‑world examples like Amazon’s evolution to microservices.
This article explains why growing business complexity and throughput demands force a system to be split and refactored, describing horizontal scaling, vertical and business splitting, database sharding, and the resulting architectural evolution toward micro‑services.
The article reviews how increasing business complexity and throughput demands drive the need to split applications and databases, adopt horizontal and vertical scaling, implement business and service-level partitioning, and evolve system architecture toward micro‑services, caching, and asynchronous processing.
This article demystifies service discovery, explains the roles of providers, consumers, and registries, explores using Redis as a lightweight registry with keep‑alive and versioning mechanisms, discusses extensions for non‑HTTP services, configuration reload, management UI, and presents a simple open‑source implementation.
Microservice architecture, introduced in 2012, breaks monolithic applications into independent services, offering benefits like scalability and flexibility while introducing challenges such as complexity, communication overhead, and testing, and the article explores its evolution, core characteristics, design patterns, implementation practices, and trade‑offs.
The article explains how distributed transactions work in microservice architectures, using inventory‑order examples and a World of Warcraft raid analogy to illustrate the XA two‑phase commit protocol, its normal and failure flows, limitations, and alternative approaches such as three‑phase commit, message‑queue and TCC transactions.
This article walks through the step‑by‑step implementation of a high‑throughput flash‑sale (seckill) service in Java, covering request flow, database schema, optimistic‑locking updates, Redis‑based rate limiting, CI scripts, and optional Kafka asynchronous order processing to achieve fast, reliable, and scalable sales handling.
This article explains how Conway's law guides functional team division in microservice architectures, describes decentralized governance, outlines various interaction and composition patterns, discusses fault‑tolerance mechanisms such as isolation, circuit breaking, rate limiting, and provides guidance on choosing appropriate service granularity.
This article explains how ServiceComb builds on Vert.x to support both reactive and synchronous communication modes, details the thread models for single and multiple connections, presents performance improvements through CAS queues and multi‑connection setups, and outlines flexible thread‑pool strategies for microservice providers and consumers.
An extensive overview of JD.com's microservice component platform explains its underlying architecture, communication technologies, service mesh (ContainerMesh), design tools based on DDD, service evaluation, migration challenges, and the platform's evolution toward a cloud‑native, self‑evolving ecosystem supporting distributed tracing, API gateways, and plugin‑based development.
The article explains the concept, functions, design goals, data models, log collection, and deployment considerations of distributed tracing systems, and compares several open‑source and proprietary solutions such as Dapper, Zipkin, Pinpoint, Alibaba Eagle Eye, and JD Hydra to guide the selection of an appropriate tracing platform.
This article explains how ServiceComb’s ServiceCenter component provides reliable microservice registration, discovery, and management through features like instance isolation, black‑white list control, asynchronous caching, heartbeat mechanisms, and self‑preservation, ensuring high availability in distributed cloud‑native environments.
The article systematically debunks six common container misconceptions—startup speed, density, image versioning, self‑healing, service discovery, and scaling—by comparing containers with virtual machines, then explains how containers fit into micro‑service and DevOps practices and outlines the scenarios where container adoption truly adds value.
This article explains Dubbo’s core RPC principles, architecture layers, design philosophy, open‑source growth, adoption by major enterprises, and upcoming plans for modularization, metadata, async support, and its progression through the Apache Incubator toward becoming a top‑level project.
The article explains how to turn a map service into an independent PHP library using Composer by creating a separate Git repository, configuring composer.json in both projects, autoloading via PSR‑4, managing dependencies, organizing code into configs, contracts, models, and custom exceptions, and highlights Composer’s advantages over Git submodule approaches for versioning and scalability.
This article explains how to protect a notification service that calls external SMS providers by using Hystrix for thread isolation, fast failure, circuit breaking, automatic recovery, and provider fallback, complete with configuration steps and Java code examples.
The article details Alibaba's fourth Middleware Performance Challenge, explaining the Dubbo‑based Service Mesh problem, the Docker‑driven test scenario, scoring methodology, and optimization suggestions such as coroutines, async communication, and caching, offering participants a comprehensive guide to excel in the competition.
This article explains the shortcomings of traditional distributed microservice testing, introduces consumer‑driven contract testing, outlines the evolution of a distributed R&D model, and provides a step‑by‑step guide with code samples for implementing Spring Cloud Contract in both provider and consumer services.
This article explains why microservice architectures need reliable communication, load balancing, fault tolerance, monitoring, tracing and circuit breaking, and shows how Istio—a cloud‑native service mesh built on Envoy—provides these capabilities, enabling blue‑green and canary deployments, traffic routing, retries, and observability within Kubernetes.
The article details how JD.com’s 7Fresh retail platform was built in just two and a half months by applying strategic DDD, virtual organization structures, extensive component reuse, and cross‑team collaboration to integrate over 60 systems and dozens of devices for both online and offline operations.
UCloud’s CTO emphasizes stable services while embracing change, leading to a lightweight Service Mesh solution that replaces costly API gateways with Istio‑derived components, enabling efficient gray releases, reduced maintenance, and seamless integration with existing services through Docker‑compose sidecars and ETCD‑based discovery.
This article analyzes the rapid growth challenges of Meituan‑Dianping's core payment flow, explains key availability metrics such as MTBF and MTTR, and presents a comprehensive set of architectural, operational, and tooling strategies—including dependency decoupling, timeout tuning, circuit breaking, and full‑link stress testing—to achieve stable, fault‑tolerant transactions.
The JD Microservice Component Platform is a comprehensive ecosystem that integrates core infrastructure, ecosystem toolchains, and foundational data services to provide communication, service discovery, flow control, security, and collaborative tools for internal and external developers, product managers, and decision makers.
This article details Xiaomi's evolution from a simple two‑server e‑commerce site to a sophisticated, decoupled architecture with the Notify asynchronous messaging system, explaining design decisions, message splitting, agent proxying, performance upgrades, and lessons for building resilient backend services.
This article outlines essential distributed system concepts—including system decomposition, concurrency, caching strategies, online vs. offline processing, push/pull communication, load limiting, service degradation, CAP theorem, and eventual consistency—to help engineers design scalable, reliable architectures for high‑traffic applications.
The article examines the reliability challenges of microservice architectures that rely heavily on synchronous RPC calls, and proposes a comprehensive solution that converts failing RPCs to asynchronous message‑queue workflows, introduces a write‑ahead‑queue for transactional consistency between databases and queues, and outlines offset management to ensure end‑to‑end fault tolerance.
This article explains why monolithic applications need to be split, outlines the preparatory steps for understanding business complexity and defining service boundaries, and provides detailed practical guidance on database vertical and horizontal splitting, global ID generation, migration, cut‑over strategies, consistency, and post‑split stability.
This article examines the limitations of traditional microservice frameworks, introduces service mesh as a solution with sidecar architecture, outlines its definition, evolution stages, and timeline, and concludes with resources for further learning and practical implementation.
This article reviews the challenges of early microservice frameworks—high technical barriers, limited multi‑language support, and intrusive code—and explains how service mesh architectures with sidecar proxies, exemplified by Linkerd, Envoy, and Istio, provide a dedicated, language‑agnostic infrastructure layer that simplifies service governance and operations.
An in‑depth look at Bilibili’s multi‑layer monitoring overhaul, detailing the shift from a monolithic Zabbix setup to micro‑service‑based ELK, Dapper, Misaka, Traceon and Lancer systems, and how layered observability improves fault detection across business, application, and infrastructure levels.
This article explains the multi‑layer data architecture design for microservice systems, covering concepts such as data usability, primary and secondary data decoupling, sharding, multi‑source data adaptation and caching, and introduces data marts to improve scalability and maintainability.
This article introduces the concept of Service Mesh, highlights Istio as a leading solution, explains the Sidecar pattern—its isolation benefits, typical implementations such as NGINX reverse proxies, and discusses when to adopt this architecture in cloud-native environments.
This article walks through the step‑by‑step evolution of a Java website—from a single‑machine setup to a multi‑tier, load‑balanced, sharded, cached, and service‑oriented architecture capable of handling billions of requests—detailing the challenges and solutions at each stage.
This article explains the fundamentals of distributed architecture, outlines its main applications such as distributed file systems, caches, databases and services, reviews its evolutionary stages from single‑server to clustered and cloud‑native designs, and discusses common operational challenges.
JarsLink is an Alibaba open‑source Java modular framework that allows runtime dynamic loading, unloading, and inter‑module communication of JAR packages, offering plug‑and‑play isolation, versioning, and resource management to simplify large‑scale backend development, reduce deployment time, and support use cases such as data integration, micro‑service testing, and backend systems.
This article discusses the importance of source code analysis, outlines key concepts in distributed systems, explains microservice architecture, highlights performance optimization techniques for Java applications, and presents practical engineering advice for modern backend development.
This article introduces Docker as an open‑source container engine, explains how it differs from traditional virtual machines, outlines its advantages, shows its relationship with micro‑services, and provides step‑by‑step installation and common command examples for getting started.
This article explains how microservice architecture reshapes functional team organization, promotes decentralized governance, defines interaction contracts such as tolerant reader and consumer‑driven contracts, and outlines service decomposition and composition patterns like proxy, aggregation, and chaining to improve agility and reduce cross‑team friction.
This article explains service branch mode, its impact on availability, asynchronous messaging, shared‑data anti‑patterns, and essential microservice fault‑tolerance techniques such as compartment isolation, circuit breaking, rate limiting, and failover strategies.
This article provides a comprehensive introduction to container technology—covering Docker's architecture, networking models, storage solutions, integration with PaaS/IaaS platforms, orchestration tools, and its impact on DevOps, micro‑services, and cloud computing ecosystems.
Effective fault tolerance is crucial for microservice stability, and this article explores core design principles and classic patterns—such as timeout retries, rate limiting, bulkhead isolation, circuit breakers, and fallback strategies—guiding developers to choose and combine the right approaches for high‑availability systems.
The article outlines the challenges faced by JD’s Java Service Framework (JSF) amid rapid microservice growth and containerization, and presents a comprehensive, multi‑layer redesign—including infrastructure, service framework, system extension, and application layers—to transform JSF into a cloud‑native microservice platform.
In this extensive interview, senior Alibaba engineer Chen Kangxian shares his experiences designing large‑scale distributed systems, live‑streaming platforms, and high‑concurrency architectures, offering practical insights on technology choices, failure handling, and career growth for software architects.
CallGraph is JD.com's internally developed distributed tracing and service governance platform that addresses the challenges of monitoring complex microservice architectures by providing low‑intrusion, low‑latency tracing, real‑time analytics, configurable sampling, and integration with JMQ, Storm, Spark, HBase, and JimDB for both operational insight and performance optimization.
Serverless computing, the latest cloud paradigm merging microservices and serverless architectures, evolves from on‑premise monoliths through SOA and containers, offering rapid deployment, cost efficiency, and scalability, while also presenting challenges such as vendor lock‑in, complexity, limited long‑running tasks, and security considerations.
This article explains Zipkin’s data model, how Spring Cloud Sleuth generates and sends Span and Annotation information, the message‑channel listener that converts Sleuth spans to Zipkin spans, debugging techniques to observe the collected data, and why the number of spans shown in Zipkin’s UI can differ from the raw count.
This article explores the core components of a microservice foundation framework—including gateways, DevOps, Docker, security, load balancing, and service discovery—examines centralized vs. in‑process load‑balancing strategies, and reviews Netflix’s open‑source stack (Eureka, Zuul, Hystrix, etc.) as a reference implementation.
This tutorial explains how Spring Cloud Sleuth creates and propagates Trace‑ID and Span‑ID across microservice calls, shows the required HTTP headers, demonstrates adding the spring‑cloud‑starter‑sleuth dependency, customizing header output, configuring logging levels, and provides runnable code samples with log output for verification.
This article explains why monolithic applications become unmanageable as they grow, outlines the advantages of breaking them into independent microservices, and discusses the architectural, operational, and testing challenges that accompany a microservice‑based design.
This article explains the fundamentals of microservices architecture, contrasting it with monolithic systems, and covers design principles, messaging patterns, integration methods, API‑gateway usage, and data decentralization to help developers build scalable, maintainable backend services.
This guide explains how to configure message partitioning in Spring Cloud Stream by adjusting consumer and producer properties—such as group, destination, partitioned flag, instanceCount, instanceIndex, partitionKeyExpression, and partitionCount—to ensure that messages with the same characteristics are consistently processed by the same instance across multiple service instances.
This article describes the background, design goals, architecture, implementation details, and lessons learned from building a low‑overhead, low‑intrusion distributed tracing system using Kafka, Elasticsearch, and OpenTracing to monitor microservice interactions and support performance analysis and DevOps decision‑making.
The article explains how client‑side and server‑side discovery rely on a service registry that stores each instance’s host and port, discusses registration options, lists common implementations such as Eureka, Zookeeper, Consul, and Etcd, and outlines the benefits and challenges of this pattern.
The article critically examines micro‑services, outlining their promised benefits such as independent development, deployment and scaling, while exposing the hidden operational, dev‑ops, state‑management, communication, versioning and distributed‑transaction challenges that can turn them into a fragile, overly complex system.
This article explains how server‑side service discovery enables clients such as API gateways to locate dynamically changing microservice instances via a router or load balancer that queries a service registry, outlining requirements, solution architecture, examples like AWS ELB, benefits, drawbacks, and related patterns.
This article explains why modern microservices need a client‑side discovery mechanism, how a Service Registry enables dynamic lookup of service instances, and outlines the advantages, drawbacks, and typical implementations such as Netflix OSS.
This article explains how using an API gateway as a single entry point enables diverse client types—desktop browsers, mobile apps, and native applications—to efficiently retrieve product details from multiple microservices while handling network constraints, service discovery, and security.
Microservice architecture, built using the Scale Cube Y‑axis approach, splits backend functionality into independent services with dedicated databases, enabling rapid development, continuous deployment, scalability, and fault isolation, while also introducing complexities such as distributed system management, testing challenges, and higher resource consumption.
Monolithic architecture, built as a single deployable unit, offers rapid development, simple deployment, and easy scaling via load balancers, but as applications grow, it introduces codebase complexity, slower IDEs, deployment challenges, limited scalability, and technology lock‑in, prompting many teams to consider microservices.
This article walks through the evolution from traditional three‑layer monolithic architecture to microservice architecture, explaining system design concepts, the drawbacks of monoliths, the benefits and challenges of microservices, and compares them with SOA, providing clear diagrams, pros and cons, and practical insights for backend engineers.
Leading architects from companies like Sogou, Ele.me, Xiaomi, Tuniu, Kuaidi, 58.com, and Tencent shared practical insights on progressively refactoring legacy systems, scaling platforms, adopting service‑oriented and streaming architectures, and balancing optimization with new business demands, offering a comprehensive roadmap for modern backend evolution.
Suning’s 2018 strategic shift transformed its traditional IT department into a technology group that integrates cloud computing, big data, AI, micro‑services and containerization across eight business units, driving a data‑driven, smart‑retail ecosystem and scaling its IT workforce to support rapid innovation.
To cope with Meituan Hotel’s exploding micro‑service complexity, the infrastructure team built the Satellite System—combining MTrace and a selective, zero‑intrusion Log4j2‑based logging pipeline that streams enriched logs through Kafka, Storm, Redis and Elasticsearch, delivering second‑level trace‑log queries and six‑month retention, dramatically speeding up debugging.
Facing over 60 million daily users and 100 K QPS, iQIYI’s Bubble platform migrated from a monolithic codebase to a business‑driven microservice architecture—splitting services by entity and function, adopting the internal RPCHUB RPC framework, establishing ownership, fault‑tolerance, monitoring and CI/CD pipelines, and addressing scaling challenges to sustain rapid growth.
This article details the design of a modular Java payment system that handles payment initiation, refunds, and callback processing by leveraging asynchronous execution with ExecutorService, RabbitMQ, Redis caching, MongoDB for persistence, and MySQL for configuration data, all illustrated with architecture diagrams and code examples.
This article explains why and when to move to distributed architecture, outlines the typical upgrade and splitting steps, and details five common distributed cluster patterns—including load balancing, leader election, blockchain, master‑slave, and consistent hashing—highlighting their trade‑offs and use cases.
This article summarizes the origins, core principles, typical evolution stages, and common toolkits of large website architecture, highlighting how network growth, performance demands, and scalability challenges drive the adoption of caching, load balancing, database sharding, CDNs, and distributed services.
This article explains the architecture and key technologies of 360’s SSP advertising engine—including flexible micro‑service layers, DAG‑based topology, rule and template management, and high‑performance Go‑based HTTP frameworks—that enable billion‑scale ad delivery with low latency and high concurrency.
The talk presented at the Global Architect Summit detailed JD Daojia's backend architecture evolution, covering physical deployment, microservice adoption, gateway design, LBS caching, order system structure, idempotency, data consistency, high‑availability strategies, gray releases, rate limiting, and stress testing, illustrating practical engineering challenges and solutions.
This article surveys the evolution of operations technology, covering microservices, SRE, DevOps, containerization, orchestration, automation, intelligent monitoring, infrastructure, database and big‑data ops, as well as security, game and fintech operational challenges, highlighting current trends and future directions for 2017.
This article explains how Pandora.js solves inter‑process communication challenges by introducing IPC‑Hub, showing simple domain‑socket examples, a concise object‑proxy model, and a practical use‑case that offloads heavy webpage‑snapshot tasks to a background process using Puppeteer.
This article presents a Chinese translation of 32 cloud design patterns originally documented by the Azure cloud team, explaining how these patterns—covering availability, data management, security, scalability, and more—can guide enterprises in migrating monolithic applications to cloud‑native architectures across any major cloud provider.
This tutorial walks through creating a Spring Boot microservice that uses Spring Cloud Stream to bind to RabbitMQ, covering project setup, required dependencies, a simple consumer implementation, application startup, log verification, core annotations, and a unit test for message production.
This article summarizes Liang Xiangdong’s talk on the API Everything framework at the Gdevops 2017 conference, detailing the motivations, design principles, lifecycle, key products such as Stargate Cluster and API Portal, and the practical impact on backend development, DevOps automation, and front‑end/back‑end separation at Ele.me.
This article describes how WiFi 万能钥匙 designed and implemented the Roma monitoring platform to handle billions of daily requests, covering background challenges, architectural principles, component design, data collection, transmission, storage, alerting, and future directions for large‑scale observability.
This weekend roundup compiles essential Spring Boot, Spring Cloud, and Spring Security articles—including quick starts, deep‑dive tutorials, microservice patterns, API‑gateway tips, and OAuth2 guides—providing developers a convenient reference list to enhance their Java backend expertise.
Google Cloud’s engineers explain how microservice architectures benefit from small, fast-deployable containers, using Docker, Docker‑Compose, and Kubernetes features such as Pods, Replication Controllers, Services, Labels, and canary releases to achieve automated, high‑availability deployments at Google’s massive scale.
