This article defines microservices, SOA, and APIs, examines their differing viewpoints and integration challenges, and proposes a combined architectural perspective that highlights how microservices can evolve from or complement traditional SOA implementations.
This article examines the challenges of securing microservice architectures and compares various authentication and authorization approaches—including SSO, distributed sessions, client‑token schemes, JWT, and OAuth 2.0—to help developers choose suitable solutions for efficient and fine‑grained access control.
This article traces the evolution of a web system from a single‑server LAMP setup through service separation, caching, clustering, read/write splitting, CDN acceleration, distributed storage, NoSQL, business decomposition, and finally to distributed services with message queues, service frameworks, and service‑bus governance.
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 presents a comprehensive design for a high‑traffic insurance O2O platform, detailing functional requirements, system analysis, storage and caching strategies, logical and service architectures, distributed transaction handling, and the chosen development stack, emphasizing simplicity, scalability, and high concurrency.
This article provides a comprehensive overview of microservice architecture, covering its definition, historical development, differences from monolithic systems, core characteristics, comparison with SOA, practical implementation concerns such as API gateways, communication, service discovery, fault tolerance, common design patterns, advantages, challenges, and a mindset shift required for successful adoption.
This article explains the role of APM in automated operations, outlines the challenges of manual thread diagnostics, and presents a one‑click thread analysis solution with a five‑stage architecture—capture, aggregation, storage, query, and deep analysis—illustrated through multiple real‑world scenarios.
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.
The article chronicles Youzan's transition from a monolithic PHP system to Java‑based microservices, outlines the architectural challenges encountered, and presents practical solutions such as Spring Boot adoption, BOM management, health‑check standardization, Hystrix circuit‑breaker patterns, automated API documentation, contract testing, and continuous integration to improve scalability, maintainability, and operational efficiency.
This article explains the fundamentals of Service‑Oriented Architecture, defines services and their essential characteristics, discusses common challenges such as consistency and security, and details bus‑based designs including broker and message‑bus patterns with practical examples.
This article chronicles a small team’s evolution from single‑repo manual deployments through service splitting, messaging middleware, SDK‑based calls, service discovery, Docker automation, and log handling, highlighting practical lessons and trade‑offs at each stage.
The article details the evolution of the Tmall client homepage from a static slot system to a personalized platform, analyzes the inefficiencies of the 2016 architecture, and introduces the 2017 TAC (Tangram App Container) solution that uses Java dynamic compilation, loading, and hot‑deployment to streamline backend development and improve stability.
58.com’s intelligent recommendation system, evolving from a C++ monolith in 2014 to a Java-based micro‑service platform, integrates multi‑layer data processing, diverse recall and ranking algorithms, and a robust microservice architecture to deliver personalized listings across housing, jobs, cars, and more.
Goldwind transformed its global wind‑farm operations by adopting a cloud‑native, container‑based microservice architecture that tackles iteration speed, hybrid‑cloud deployment, and IoT big‑data challenges, enabling faster development, cost reduction, and advanced energy‑forecasting capabilities.
The article details Meituan’s overseas‑hotel backend system—from its initial construction using reusable services and mature frameworks, through custom micro‑service design emphasizing simplicity and extensibility, to extensive optimizations for availability, performance, and scalability, and finally team‑building practices that together ensure reliable evolution as business demands grow.
This article explains how microservices evolved from SOA as a fine‑grained implementation, compares their concepts, benefits, and drawbacks, and provides practical guidance for choosing architectures, communication protocols, and frameworks—especially in Java‑based systems.
This guide walks through creating a Spring Cloud Config server backed by a Git repository, configuring it, exposing configuration via REST endpoints, and building a Spring Boot client that retrieves and binds those configurations, complete with code snippets and URL patterns.
This article explains how to configure Feign and Hystrix so that HTTP error responses from a downstream service are wrapped in a HystrixBadRequestException, allowing the calling service to receive the original status code without activating Hystrix's circuit‑breaker logic.
This article details how Alibaba's RDC platform combines layered automated testing, test‑driven continuous delivery, and comprehensive online quality monitoring to overcome the myth of a single silver‑bullet solution in large‑scale software development.
This talk outlines how China’s Guangfa Bank built, refined, and scaled its big‑data platform since 2014, covering data positioning, system architecture optimization, delivery model improvements, team restructuring, and real‑world use cases that demonstrate the platform’s impact on risk control, marketing and operational efficiency.
This article offers a practical, non‑technical overview of the differences between Service‑Oriented Architecture (SOA) and Microservice Architecture (MSA), discussing concepts such as ESB, service granularity, communication protocols, complexity, maintainability, high‑concurrency handling, and Java framework choices for building robust systems.
This guide shows how to build a Spring Cloud consumer that registers with Eureka, configures LoadBalancerClient and RestTemplate, and calls a provider service’s endpoint using load‑balanced discovery, complete with Maven dependencies, configuration files, and full Java code examples.
Uber’s engineering team chronicles the evolution of its distributed tracing system—from the early Merckx pull‑based solution and TChannel integration to the open‑source Jaeger platform—detailing architectural shifts, sampling strategies, multi‑language client libraries, and the move toward a fully cloud‑native, end‑to‑end observability stack.
This article explains the concept, benefits, and implementation details of a unified error‑code management platform, covering code allocation, handling strategies in microservice architectures, API security considerations, and performance optimizations to reduce development friction and improve system reliability.
The article examines the rise of microservices, outlines their key characteristics, recounts a company's painful transition from a monolithic Tomcat‑based architecture to a decentralized microservice ecosystem, and shares the practical challenges and pitfalls encountered during the migration.
This guide explains how to enhance Spring Cloud's Ribbon with custom rules that enable weight‑based traffic distribution and label‑driven routing, covering project setup, core microservice components, implementation approaches, testing procedures, and practical examples for real‑world microservice deployments.
This week’s tech roundup highlights Alibaba’s data clash with SF Express, Node.js v8’s new features, the launch of China’s Big Data Security Lab, Istio’s service mesh for micro‑services, TensorFlow Lite for mobile AI, Connecterra’s AI livestock monitoring, AlphaGo’s inspirational role, Ma Huateng’s cloud‑economy insights, and Siri’s expanded third‑party support.
The article examines why a large‑scale platform refactoring presents an opportunity to redesign services, traces the conceptual roots of microservices through influential software‑engineering masters and methodologies such as DDD and SOA, and argues that microservices are an evolutionary, not silver‑bullet, solution that must be applied with careful strategic and tactical analysis.
The article explains how to break large transactions into small atomic operations combined with asynchronous messaging, describes ACID properties, presents banking and flow‑recharge scenarios, compares local and distributed (flexible) transactions, and details micro‑service architecture, compensation and async strategies to achieve eventual consistency.
These notes distill Mark Richards' O'Reilly guide on software architecture patterns, explaining layered, event‑driven (mediator and broker), microkernel, microservices, and space‑based architectures, their key concepts, examples, trade‑offs, and evaluation criteria to help developers select the most suitable pattern for their projects.
The article narrates a Chinese state‑owned enterprise’s struggle with heterogeneous legacy systems, the introduction of an SOA strategy, and a contrasting startup’s shift to microservices, highlighting technical, operational, and cultural challenges of modernizing large‑scale software.
The article explains Serverless and Functions‑as‑a‑Service, their relationship with micro‑services, typical use cases such as bursty workloads and event‑driven data processing, and discusses the operational, cost, and strategic implications for cloud platforms like Alibaba Cloud.
This article shares JD's practical experience of scaling its phone‑recharge platform by introducing caching, concurrent processing, micro‑service decomposition, vertical‑and‑horizontal sharding, read/write separation, resource isolation, and gray‑release deployment to meet rapidly growing user demand.
Microservices architecture introduces technical concerns such as service registration, discovery, load balancing, health checks, front-end routing, fault tolerance, dynamic configuration, and framework selection, with common solutions ranging from centralized and in-process load balancers to Netflix and Spring Cloud components.
This article explains the four essential components of Spring Cloud Zuul filters, details the request lifecycle across pre, routing, post, and error stages, and provides an in‑depth overview of the built‑in core filters and how to extend them for custom gateway behavior.
This article explains how blockchain, originating from Bitcoin, serves as a distributed ledger that reduces trust costs in complex multi‑party business scenarios, outlines public, private and consortium chain models, and details how a dedicated blockchain gateway integrates seamlessly with microservice architectures for reliable communication, event handling, data consistency and reconciliation.
This article chronicles Toutiao’s evolution from a monolithic Python/C++/PHP stack to a large‑scale Go‑based microservice architecture, detailing the reasons for adopting Go, the design of the kite framework, concurrency models, timeout control, performance tuning, monitoring, and a reusable DAO component for efficient RPC aggregation.
This article outlines the critical backend components and services—such as API gateways, MVC/IOC/ORM frameworks, caching, databases, search engines, message queues, unified authentication, configuration management, service governance, scheduling, logging, and data processing pipelines—that together enable stable, high‑availability, and maintainable online applications.
This article explains microservice architecture versus monolithic design, discusses communication, service discovery, ordering, and messaging strategies, and details GeTui’s practical implementation using OpenResty, API gateways, Zookeeper, and DevOps automation.
This article explains the differences between monolithic and microservice architectures, introduces Docker as a key tool for microservices, and details how a Container‑as‑a‑Service (CaaS) platform can provide service discovery, routing, logging, monitoring, auto‑scaling, SLA enforcement, and deployment strategies to simplify development and operations.
This article explains how to design a payment system by covering product classification, module functions, business processes, and reference architectures, illustrating the role of microservice proxies, risk assessment, and integration with popular platforms like Alipay, WeChat Pay, and PayPal.
The article details Hulu's evolution from a simple web video service to a multi‑device platform, highlighting the scalability, micro‑service architecture, DASH streaming, and comprehensive quality monitoring that enable consistent live streaming experiences across diverse US devices.
This article examines how Agile, DevOps, microservices, and Docker have risen together in recent years, analyzing Google Trends data to illustrate their intertwined growth and explaining why Docker is seen as essential for rapid software delivery within modern DevOps and microservice ecosystems.
This article explains the principles of distributed transaction design, covering ACID fundamentals, typical banking and e‑commerce scenarios, various transaction models such as two‑phase, compensation, asynchronous and best‑effort notifications, and presents a micro‑service architecture with concrete flow diagrams and scaling strategies for a high‑throughput traffic‑recharge platform.
This article introduces Vesta, a Java‑based multi‑scenario distributed ID generator, covering its design goals such as global uniqueness, rough ordering, reversibility and manufacturability, its architecture, publishing modes, performance benchmarks, and step‑by‑step deployment instructions for various deployment scenarios.
An in‑depth comparison of Ansible and SaltStack evaluates response speed, security, maintenance overhead, and syntax readability, concluding that despite slower performance, Ansible’s superior security and simpler operations make it the preferred automation solution for large‑scale, especially financial, environments.
This article examines the challenges of achieving consistency in large‑scale distributed service systems, outlines common inconsistency scenarios such as split‑brain and lost updates, and presents practical patterns—including ACID/BASE trade‑offs, two‑phase and three‑phase commit, TCC, query, compensation, and reliable messaging—to guide engineers in designing robust, eventually consistent architectures.
This article outlines how to transform cloud computing from a barrier into a foundation for business success by defining Cloud‑Native principles, recommending public‑cloud adoption, project engineering practices, service‑oriented thinking, micro‑service implementation with Kubernetes, and DevOps integration, providing concrete guidance and trade‑offs for each step.
This article explains how a decentralized microservice and SOA architecture, combined with cloud deployment, service registration, gateways, and unified APIs, enables high‑performance, high‑availability, and low‑coupling smart campus systems that support both mobile and PC applications while simplifying development, testing, and operations.
This article explains why distributed systems need tracing, outlines design goals, compares major implementations like Zipkin, EagleEye, and Hydra, and details the data collection, storage, and analysis pipelines that enable end‑to‑end visibility and performance optimization in large‑scale services.
Learn how to launch several Spring Cloud microservice instances on a single machine without manually editing configuration files by leveraging random ports and adjusting Eureka instance IDs for proper registration.
The article explores DevOps concepts, recounting personal experiences with legacy systems, the evolution of continuous integration and delivery, the promises and pitfalls of microservices, deployment challenges, orchestration tools, and modern container‑based solutions like Docker and Kubernetes, emphasizing a pragmatic path toward immutable infrastructure.
This article traces the evolution of software engineering tools leading to DevOps, highlights common transformation pitfalls, outlines core DevOps practices such as autonomous small teams, traceable toolchains, real‑time metrics, and describes the surrounding ecosystem, offering practical guidance for organizations adopting DevOps.
The article describes Baidu's comprehensive code development collaboration platform, detailing its multi‑stage architecture evolution, five‑level code management model, challenges of massive scale, and the enterprise‑grade SaaS solutions that enable high availability, scalability, security, and multi‑tenant isolation.
This article explains how to solve the problem of undefined results when making asynchronous HTTP requests in a Node.js microservice by passing a callback function that receives the response data and any error, allowing the data to be accessed outside the request handler.
The article examines common challenges in legacy continuous‑integration pipelines—long build times, unstable tests, and complex dependencies—and presents a systematic, Theory‑of‑Constraints‑based approach that includes parallelization, mocking, infrastructure upgrades, test isolation, contract testing, and monitoring to improve build speed, reliability, and overall delivery efficiency.
The article analyzes the rapid growth‑induced technical debt of a sales platform and details a multi‑layered architectural optimization—including data‑layer redesign, monolith decomposition, and service‑oriented transformation—while discussing associated challenges and future service‑governance improvements.
This article details how Tencent Games built, customized, and continuously optimized a Kubernetes‑based container platform over three years to support tens of thousands of game containers, covering deployment modes, scheduler enhancements, network solutions, resource quotas, monitoring, storage, and the transition to micro‑service architectures.
This article details how Tencent's game operations team redefined operational services, introduced micro‑service architecture, applied big‑data driven recommendations, and built intelligent, automated pipelines for server opening, merging, version releases, and download services, achieving significant efficiency and cost gains.
This article examines VIPshop's transformation from a single‑application LAMP system to a vertically split and finally distributed service‑oriented architecture, detailing the business model, key design requirements, platform governance, and the technical services that enable a scalable e‑commerce operation.
This tutorial walks through configuring Spring Cloud Ribbon and Spring Cloud Feign to perform client‑side load balancing for a compute-service, covering prerequisite setup, Maven dependencies, application code, REST client implementation, and verification of balanced requests across multiple service instances.
This article chronicles Xiaomi's e‑commerce platform evolution, detailing the shift from a simple monolithic design to a modular, sharded, and cloud‑native architecture that leverages async messaging, horizontal database partitioning, flash‑sale systems, dual‑data‑center caching, and sophisticated monitoring to handle massive traffic spikes.
Alibaba’s transformation from e‑commerce leader to tech powerhouse is highlighted by its Feitian middleware platform, a cloud‑based, highly available solution that supports diverse industries, enables massive transaction volumes, and exemplifies the evolution of large‑scale distributed architectures pioneered since Alibaba’s early IOE days.
This guide walks through setting up Spring Cloud, explains microservice architecture, and provides step‑by‑step instructions with code samples for creating a Eureka service registry, a compute service provider, and switching to Consul for service discovery in a cloud‑native Java environment.
This article explains why Node.js can be a better choice than Nginx for dynamic reverse‑proxy scenarios such as micro‑service gateways, and provides a step‑by‑step tutorial—including installing http‑proxy, creating a mock service, building a proxy server, and testing it.
The article outlines the complex business logic of JD Daojia's transaction system and presents architectural decisions such as service setization, database sharding, frontend‑backend separation, parallel execution, asynchronous processing, dependency governance, and future enhancements to improve scalability, reliability, and performance.
This article introduces the upcoming “Spring Cloud Practical Tips” series and focuses on version dependency issues, common Feign errors, and recommended version pairings, advising developers to follow official Spring Cloud compatibility charts and favor the latest Camden release with Spring Boot 1.4.x for enhanced features.
Over three years, a small fintech company transformed its platform from a single‑server PHP/Java stack to a micro‑service‑based Spring Cloud architecture, undergoing four major upgrades that introduced distributed systems, SOA governance, big‑data pipelines, MongoDB replication, Redis caching, and open‑source tools, enabling transaction volumes exceeding one hundred billion.
This article compares the CI/CD pipelines and Git branching models of two micro‑service projects, highlighting their deployment workflows, automation levels, visualisation, feedback speed, and trade‑offs to help developers and operations engineers choose an appropriate strategy.
This article traces the evolution of internet‑scale technical architecture across three eras—single‑machine, cluster, and distributed—detailing the motivations, core patterns, advantages, and drawbacks of monolithic, layered, data‑separated, cached, load‑balanced, CDN‑accelerated, redundant, service‑oriented, sharded, and microservice designs.
The article explains how growing business complexity and legacy code make monolithic systems hard to maintain, and shows how microservice architecture—by isolating functionality, improving scalability, supporting DevOps, and fitting cloud environments—delivers agility, lower error rates, and easier resource management.
This article outlines the most important Node.js best practices for 2017, including adopting ES2015, using Promises, following coding standards, deploying with Docker, monitoring with Prometheus or Trace, enhancing security with checklists, learning micro‑services, attending conferences, semantic versioning, and using LTS releases.
This article explains the reasons for breaking up tightly‑coupled monolithic systems, outlines preparation steps such as assessing business complexity and defining service boundaries, and provides detailed practical guidance on database sharding, migration, query refactoring, cut‑over plans, consistency, and post‑split stability.
This article shares the engineering team’s experience of building a high‑growth, reliable backend for English Fluently, covering inter‑service communication with gRPC, service discovery, Docker‑based deployment, health‑checking, monitoring, autoscaling, Kubernetes orchestration, and multi‑cell availability strategies.
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.
The article analyzes how the rapid adoption of microservices and container virtualization, especially Docker, boosts software agility and adaptability, while highlighting the critical role of stateful services, the challenges of storage in containers, and the concrete benefits of running both stateless and stateful components within containers.
This article explores how to build a high‑traffic insurance O2O platform for tens of millions of users by emphasizing simple micro‑service architecture, detailed functional requirements, performance targets, distributed storage, caching, service registration, and a practical technology stack for reliable, extensible backend development.
From its origins at the 2008 Agile conference to the modern CALMS framework, this article traces DevOps’s evolution, compares traditional, DevOps 1.0 and 2.0 approaches, and outlines key Chinese practices such as containers, continuous deployment, micro‑services, and enterprise best‑practice recommendations.
This article provides a comprehensive overview of Netflix Eureka, explaining its background, reasons for adoption, core architecture, a step‑by‑step demo, and detailed implementation of the Eureka server, service provider, and service consumer within a Spring Cloud micro‑services environment.
This article examines the fundamental challenges of achieving consistency in distributed systems, explains the CAP theorem, compares two‑phase and three‑phase commit protocols, explores XA transactions, and presents practical compensation patterns such as local message tables, non‑transactional and transactional MQ designs, highlighting their trade‑offs and applicability.
This article presents a comprehensive case study of the EMC containerized delivery platform, detailing how Docker, Kubernetes, and automated image building are leveraged to achieve continuous delivery for a large‑scale microservices project, and discusses the system’s architecture, image standardization, environment governance, and future enhancements.
As microservice architectures grow, service calls become increasingly complex, involving dozens of services and teams, making rapid fault localization and comprehensive data analysis critical; distributed tracing systems address these challenges by providing end‑to‑end visibility, low‑overhead instrumentation, and scalable monitoring across large‑scale applications.
This article explains the fundamental ideas behind microservices, compares them with traditional SOA, discusses when to adopt microservices, outlines design principles, explores technology selections such as Spring Cloud and Docker, and addresses common challenges like service discovery, transaction handling, and operational costs.
This article explains why microservices are chosen over monolithic architectures, outlines their key characteristics, reviews popular frameworks such as Netflix's stack and Spring Cloud, and discusses essential concerns like service discovery, load balancing, security, configuration, monitoring, and fault tolerance.
The article traces DevOps from its 2008 Agile conference origins, explains the CALMS cultural model, compares traditional, DevOps 1.0 and DevOps 2.0 practices, and highlights containers, continuous deployment, and micro‑services as the key technologies shaping today’s enterprise software delivery.
This article explains the origins, key characteristics, speed advantages, and step‑by‑step implementation of microservice architecture, showing how small, independent, loosely‑coupled services enable rapid development, continuous delivery, and productized deployment in modern cloud‑native environments.
The article examines how containerization, micro‑services, and cloud‑native patterns have reshaped software architecture, challenged traditional IOE stacks, and forced enterprises to rethink organization, tooling, and development practices to stay competitive in an accelerating technological landscape.
The Double 11 shopping surge set new sales and user‑experience records, prompting the China Software Developer Conference to host a comprehensive e‑commerce architecture track from November 18‑20 that covered international infrastructure, global regional deployment, large‑scale product systems, startup‑scale platforms, cloud migration, smart pharma solutions, and platform governance.
This article explores how software development has transformed over the past decade, highlighting the shift from monolithic architectures to service‑oriented, containerized, and microservice models, and explains why improving developer efficiency and experience is the core driver of this evolution.
The article introduces MTrace, Meituan‑Dianping’s large‑scale distributed session tracing system, explaining its call‑chain concept, architecture, data‑embedding SDK, trace and span identifiers, APIs for transparent data propagation, and how it enables bottleneck detection, performance optimization, and comprehensive monitoring across heterogeneous backend services.
The article explores the rise of experience APIs and Backends for Frontends, discussing how microservice architectures, API facades, custom payloads, media types, Prefer headers, and GraphQL can be used to tailor APIs for diverse client platforms while weighing the trade‑offs for small versus large teams.
MTrace, Meituan‑Dianping’s internal distributed tracing platform, assigns a global 64‑bit traceId to each request, instruments RPC, HTTP, database and messaging calls, aggregates data via Kafka into HBase and Hive, and visualizes the full call chain to pinpoint network cross‑datacenter traffic, latency bottlenecks, redundant calls, and correlated exceptions, thereby enabling systematic service‑level optimization.
This article examines how increasing software productivity drives the evolution of development models—from traditional waterfall through agile to microservices—and how full‑feature teams adapt production relations to maximize efficiency and creativity.
This article details Meituan's technical approach to handling massive traffic spikes during large‑scale promotions, covering background of the O2O deal platform, traffic‑model construction, capacity‑budget calculations, micro‑service architecture evolution, pressure‑test strategies, and the PTP performance‑testing environment used to validate system limits.
Peter Marton, co‑founder and CTO of RisingStack, argues that Node.js excels for microservices due to its efficiency, performance, and developer happiness, citing PayPal’s reduced codebase, Netflix’s faster startup and scaling, and GoDaddy’s hardware savings after migrating from .NET.
Alibaba architects attended the SpringOne conference in Las Vegas, sharing insights on emerging technologies such as ReactiveX, Ratpack, Java 9 modules, Spring 5 and 1.4, Zipkin, XRebel, PaaS platforms, serverless computing, cloud‑native principles, Agile, DevOps, and microservices, highlighting both global trends and challenges for Chinese cloud providers.
This article explains how breaking monolithic applications into Node.js‑based microservices improves scalability, deployment speed, and developer productivity, illustrated with real‑world case studies from PayPal, Netflix, and GoDaddy. It also highlights the efficiency of npm, the non‑blocking I/O model, and the rapid adoption by modern development teams.
Facing massive transaction volumes and stringent regulatory demands, GF Securities re‑engineered its legacy monolithic trading platform using container and micro‑service technologies, adopting cloud‑native principles to achieve high reliability, low latency, auto‑scaling, and proactive, business‑level monitoring for a resilient, anti‑fragile system.
This article examines the evolution from traditional monolithic access security to modern microservice architectures, outlines key design principles, compares four common authentication schemes, and demonstrates a Spring Cloud Security implementation using OAuth2 and UAA for fine‑grained, token‑based protection.
