This article details migrating from Spring Cloud/OpenFeign to Apache Dubbo 3 with Spring Boot 3, covering Triple protocol over HTTP/2, binary serialization, service governance (timeouts, retries, load balancing), streaming, observability, and production pitfalls with benchmark comparisons showing 3-5x throughput gains.
This comprehensive guide compares Dubbo, gRPC, and Feign across eight critical dimensions including protocols, serialization, performance, cross-language support, service discovery, circuit breaking, streaming, and hybrid architecture coordination, with detailed interview questions and answers for each.
This article compares Dubbo, gRPC, and Feign across circuit breaking, streaming, contract management, learning curves, and real-world scenarios, providing a decision matrix and a Spring Cloud Alibaba hybrid architecture where all three coexist for external HTTP, internal high-frequency Java, and cross-language algorithm services.
The article walks through three real‑world Java service scenarios—high‑frequency internal calls, cross‑language algorithm services, and Spring Cloud gateway integration—comparing Dubbo, gRPC and OpenFeign on protocol, serialization, latency, throughput, cross‑language support, service governance and discovery, and finally presents a decision matrix and a mixed‑architecture demo.
This article provides a deep dive into Dubbo’s core architecture, registry resilience, protocol choices, load‑balancing strategies, cluster fault‑tolerance policies, SPI enhancements, the shift from interface‑level to application‑level service discovery, timeout‑cascade pitfalls, and how to run Dubbo alongside Spring Cloud in a Spring Boot 3 + Nacos environment.
Splitting a monolithic order system into separate services introduces challenges such as scattered routing, uncontrolled configuration changes, and fragmented logs, which can be mitigated by implementing a unified API Gateway, a centralized Nacos configuration center, and comprehensive SkyWalking tracing to ensure observability, fault isolation, and safe incremental releases.
A tiny field‑addition and rename in an order service caused a cascade failure in a three‑year‑old reconciliation job, illustrating how any incompatible change in a system handling tens of millions of QPS can trigger an avalanche, and the article explains why version management, compatible design, multi‑version coexistence, and disciplined governance are essential to keep such large‑scale services reliable.
The article examines how to choose between Dubbo and Spring Cloud for high‑traffic microservice systems, analyzing communication models, thread and connection handling, governance capabilities, real‑world e‑commerce scenarios, and provides practical guidance on combining HTTP gateways, RPC, and asynchronous messaging for scalable, resilient architectures.
This article explores microservices architecture beyond basic decomposition, covering decoupling principles, service boundary identification, governance pillars (observability, traffic control), distributed transaction patterns, data management strategies, API design best practices, infrastructure choices (Kubernetes, Service Mesh), organizational alignment via Conway's Law, and when to avoid microservices.
Using the classic tale Journey to the West, the article maps each disciple to a microservice, explains the shift from monolith to microservices, and illustrates service governance, load balancing, service discovery, fault tolerance, and distributed transactions through vivid analogies and concrete examples.
The article explains why, despite the apparent speed of direct internal service calls, using an API gateway provides essential benefits such as unified governance, version‑aware routing, protocol translation, security isolation, and high‑availability traffic buffering, making it a worthwhile trade‑off in most microservice environments.
This article provides a detailed technical walkthrough of a typical payment platform architecture, covering the overall system overview, core transaction and payment modules, service governance mechanisms such as unified context and data consistency, and practical production practices like performance testing and asynchronous processing.
This article explores the fundamental architecture of a payment platform, detailing the separation of transaction and payment cores, the key modules such as transaction abstraction, payment orchestration, service governance, data consistency, asynchronous processing, performance testing, and practical strategies for stability and scalability.
This article explains why remote procedure call (RPC) remains essential for microservice communication, detailing its historical roots, the limitations of HTTP, the multi‑step RPC workflow—including service discovery, serialization, network transmission, dynamic proxies, and governance—and how RPC and HTTP complement each other in modern architectures.
Apache Dubbo Admin 0.7.0 transforms the classic registry‑center console into a Kubernetes‑native control plane, adding unified traffic‑governance UI, deep observability with Grafana dashboards, multi‑registry support, event‑driven architecture, and a roadmap for further service‑governance and AI‑assisted features.
Apache Dubbo Admin 0.7.0 transforms the traditional registry console into a Kubernetes‑native control plane, adding hybrid registry support, unified traffic governance, deep observability, and multi‑registry isolation while redesigning the backend with Go and client‑go integration.
This article breaks down the architecture of a generic payment core system, covering the transaction and payment cores, service governance, data consistency, asynchronous processing, performance testing, and stability measures to help engineers build robust payment platforms.
This article walks through the complete architecture of a payment platform, detailing the transaction and payment cores, their interactions, service governance, data consistency, DB sharding, asynchronous processing, performance testing, and practical production practices for building robust backend payment systems.
This article walks through the architecture of a typical payment system, detailing the transaction and payment cores, channel gateways, accounting, service governance, asynchronous processing, performance testing, and stability measures, while also mentioning a promotional AI community segment.
This article chronicles the decade‑long evolution of WeChat Reading’s backend, detailing architectural layers, RPC framework innovations, storage migrations, account system redesign, book data platform construction, and modern content retrieval techniques that together enable high availability and scalability.
Backend ArchitectureService Governancebook data platform
This article walks through a typical payment system architecture—covering the transaction and payment cores, service governance, data consistency, asynchronous processing, performance testing, and production best practices—providing a comprehensive view for engineers building robust financial platforms.
Asynchronous ProcessingService Governancepayment system
This article traces the evolution of internet architecture from monolithic and MVC designs through multi‑application and distributed systems, explains service‑oriented architecture and its benefits, introduces Dubbo‑based service governance, and outlines the core concepts, features, and implementation approaches of microservices.
This article explains why rate limiting is essential for high‑traffic microservices, outlines the key design considerations, compares major algorithms such as fixed‑window, sliding‑window, leaky‑bucket and token‑bucket, and details how Tencent Service Framework (TSF), Polaris, and TSF‑Consul implement distributed rate limiting with practical configuration examples and post‑limit handling strategies.
This article presents a comprehensive overview of a typical payment system architecture, detailing the division between transaction and payment cores, their interactions, service governance, data consistency, asynchronous processing, and practical production practices for building stable, scalable backend payment services.
This article explains why rate limiting is essential for microservice reliability, outlines the key factors to consider before applying limits, compares major algorithms such as fixed‑window, sliding‑window, leaky‑bucket and token‑bucket, describes post‑limit actions, and details how Tencent Service Framework (TSF) implements configurable, tag‑based rate limiting in cloud‑native environments.
Microservice architecture, once a buzzword, breaks monolithic applications into independent services, but introduces challenges such as service governance, communication, gateway management, fault tolerance, and tracing; the article outlines these issues and presents practical solutions like Consul/Eureka, REST/RPC, API gateways, Hystrix, and tracing tools.
This article introduces a compile‑time, zero‑intrusive auto‑instrumentation technique for Go that enables comprehensive monitoring, service governance, security checks, and custom extensions across popular frameworks, allowing developers to inject custom logic without modifying existing source code.
Service Governanceauto-instrumentationcloud-native
This article presents a comprehensive overview of payment system architecture, detailing core transaction and payment modules, service governance, data consistency, asynchronous processing, performance testing, and practical production practices for building a robust backend payment platform.
This article introduces a zero‑intrusive compile‑time automatic instrumentation framework for Go, explains its preprocessing and code‑injection mechanisms, and provides modular extension principles with concrete examples such as HTTP header logging, sort algorithm replacement, SQL injection protection, and gRPC traffic control.
This article introduces a compile‑time, zero‑intrusion auto‑instrumentation technique for Go applications that enables seamless monitoring, service governance, security checks, and traffic protection through modular JSON‑driven code injection, with practical examples covering HTTP headers, sorting algorithms, SQL injection prevention, and gRPC traffic control.
This article compares Spring Cloud and Dubbo, detailing their core design philosophies, communication protocols, service governance features, and ideal application scenarios to help developers choose the most suitable microservice framework for their projects.
The article recounts how a large group‑level development organization tackled siloed, duplicate systems by creating a public‑service team, evolving into a platform strategy, adopting a unified Dew micro‑service framework, establishing middle‑platform standards such as the 6S model, and finally building a BIOS integration layer to achieve coherent, scalable engineering and management practices.
This guide explains how to use Alibaba Cloud MSE to add traffic control, circuit breaking, gray release and other governance capabilities to Go microservices without modifying business code, covering compilation injection, deployment steps, and practical demo configurations.
This article explains microservice service governance, covering registration and discovery, load balancing, rate limiting, circuit breaking, dynamic configuration management, and monitoring using tools like Nacos, Dubbo, Sentinel, Prometheus, and SkyWalking.
In 2023 NetEase Cloud Music executed its largest ever data‑center migration, moving over 20,000 applications and more than one million queries per second to a new Guizhou facility while meeting zero‑downtime, strict latency and bandwidth limits through a batch‑wise, cross‑team strategy that incorporated automated upgrade platforms, standardized operations, and extensive risk‑mitigation measures.
Data Center MigrationDistributed SystemsService Governance
This guide walks through the PolarisMesh polaris-server startup process, detailing configuration loading, bootstrap sequencing, and the initialization of core modules such as apiserver, cache, auth, namespace, service discovery, and config center, with code snippets and structural diagrams.
The article explains Sermant's classloader architecture, plugin mechanism, class isolation, unified dynamic configuration, and logging capabilities, providing step‑by‑step guidance for building service‑governance plugins from basic to advanced features.
This article presents a comprehensive overview of how to design and implement a recommendation system using cloud‑native technologies, covering the cloud‑native stack, system architecture, key design considerations such as virtualization, micro‑service migration, service governance, resilience, and stability through chaos engineering.
This article presents a detailed three‑step plan used by Zhezhuan to detect and eliminate zombie services, unused code methods, and obsolete component dependencies through monitoring, static analysis with Spoon, and Java‑agent based runtime tracing, achieving significant resource savings and improved code health.
This article by a senior architect provides a detailed overview of payment system architecture, covering transaction and payment cores, system interactions, service governance, asynchronous processing, and production practices, while also offering practical performance testing and stability strategies.
Asynchronous ProcessingService Governancebackend development
This article walks developers through Sermant’s architecture, explaining its plugin mechanism, class isolation, and how to build practical plugins with basic capabilities, unified dynamic configuration, and unified logging, while showcasing real‑world examples and tips for efficient development.
This technical presentation describes JD's data service platform, covering its origin, performance optimizations, flexible API generation, scaling to massive metrics, caching strategies, service orchestration, governance, and a Q&A on security and data‑source flexibility.
This article presents a comprehensive overview of a typical payment system architecture, describing the transaction core, payment core, service governance, asynchronous processing, performance testing, and practical production practices, while illustrating each component with diagrams and implementation details.
Asynchronous ProcessingService Governancebackend development
This article explains how to achieve 24/7 service availability through comprehensive monitoring, fault handling, release management, and capacity planning, covering alarm types, batch processing, traffic and resource metrics, fault causes and mitigation, deployment strategies, scaling commands, and service degradation techniques.
Service Governancecapacity planningfault management
This article outlines the essential design principles, client optimizations, CDN usage, clustering, caching, database tuning, and service governance techniques needed to create robust high‑traffic, high‑concurrency systems that scale reliably and maintain performance.
This article outlines the essential principles, architectural patterns, client optimizations, CDN usage, clustering, caching strategies, database tuning, and service governance techniques required to design, build, and maintain high‑traffic, high‑concurrency backend systems effectively.
Vivo’s account platform, serving 270 million users and over 100 billion daily requests, achieves high‑performance stability through disciplined service splitting, hierarchical dependency control, layered caching and sharding strategies, and comprehensive multi‑layer monitoring that together ensure scalability, availability, and rapid fault diagnosis.
This article outlines the essential design principles, client‑side optimizations, CDN usage, clustering, caching, database tuning, and service governance techniques required to build and maintain high‑traffic, high‑concurrency backend systems that are reliable, scalable, and performant.
This article explores the comprehensive architecture of modern payment systems, detailing the interaction between transaction and payment cores, system components such as gateways, accounting, service governance, data consistency, async processing, and practical performance and stability practices used in large‑scale financial platforms.
This article explores the comprehensive architecture of a payment platform, detailing the transaction and payment cores, service governance, data consistency, asynchronous processing, and production practices, illustrated with diagrams to help engineers design robust, scalable payment systems.
This article presents a detailed overview of typical payment system architecture, describing the division between transaction and payment cores, their interactions, key modules such as transaction core, payment core, channel gateways, data consistency, service governance, and practical production considerations like performance testing and stability management.
This article explains the core components and interactions of a typical payment system, describing the transaction and payment cores, their abstractions of payment types, service governance mechanisms, data consistency strategies, asynchronous processing, and practical production practices for high‑performance, reliable payment platforms.
This guide shows how to use Alibaba Cloud MSE to non‑intrusively add service registration, discovery, and governance—including full‑chain gray release—to existing Spring Boot applications, with step‑by‑step instructions, demo setup, and practical code snippets.
The Punica system unifies AI inference development, testing, deployment, and maintenance on a FaaS‑based one‑stop platform that automates resource scheduling, self‑healing, and monitoring, supporting multiple frameworks and GPUs, thereby doubling onboarding speed, quintuple scaling efficiency, and reclaiming hundreds of GPU cards.
AI inferenceAutonomous OperationsFaaS architecture
This article presents a detailed overview of payment system architecture, describing the transaction and payment cores, their interactions, service governance, asynchronous processing, data consistency, and practical production practices, while illustrating each concept with diagrams and code snippets.
This article presents a comprehensive overview of a typical payment system architecture, detailing the transaction core, payment core, service governance, data consistency, asynchronous processing, and production practices such as performance testing and stability management.
This article presents a detailed analysis of modern payment system architecture, covering the transaction and payment cores, service governance, data consistency, asynchronous processing, and practical production practices such as performance testing and stability management, illustrated with numerous diagrams.
Asynchronous ProcessingService Governancebackend development
This article explains the need for service‑governance standardization in cloud‑native microservices, outlines the challenges posed by diverse technology stacks and mixed infrastructures, presents a three‑layer standardized solution with PolarisMesh as the default implementation, compares it to XDS, and describes ecosystem integration and future plans.
This article presents JD's data service platform, describing its origin, performance optimizations, flexible API generation, caching strategies, service orchestration, and governance, and includes a Q&A that addresses security, performance, and multi‑source data handling challenges.
This article outlines a seven‑stage microservice lifecycle and presents sixteen practical principles covering planning, design, implementation, invocation, release, governance, scaling, and deprecation to help architects build robust, maintainable microservice systems.
This article explains how modern payment platforms are structured into transaction and payment cores, details their interactions, service governance, data consistency, asynchronous processing, and practical production practices such as performance testing and stability management.
This article describes how Zhaozhuan’s testing environment evolved through three versions—physical isolation, automatic‑IP‑tag routing, and manual‑tag routing—detailing the architectural background, implementation principles, advantages, drawbacks, and supporting tools that dramatically reduced deployment time and resource consumption while introducing new operational challenges.
This article presents a comprehensive overview of widely adopted microservice technology stacks, including governance frameworks like Apache Dubbo and Spring Cloud Alibaba, CI/CD tools, container orchestration, and various application services, while also offering practical selection guidance for developers and product teams.
Facing rapid growth and complex service interactions, Huolala transitioned from a simple PHP‑based architecture to a self‑developed microservice framework, combining data and control planes, custom RPC protocols, and robust governance, while explaining why existing solutions like Dubbo and Istio were unsuitable.
This article shares Ctrip's practical experience in microservice governance, detailing the background, common pitfalls such as excessive service granularity and cyclic dependencies, and presenting concrete goals, principles, and strategies that led to significant improvements in stability, performance, and development efficiency.
This article presents a comprehensive overview of payment system architecture, detailing the core transaction and payment modules, system interactions, service governance, data consistency strategies, asynchronous processing, and practical production practices such as performance testing, stability management, and service isolation.
The article presents a comprehensive overview of backend architecture, covering product analysis, microservice design principles, real‑time messaging evolution, load‑balancing migration from HAProxy to Nginx, request idempotency techniques using AOP and Redis, and a detailed discussion of service governance challenges and solutions.
This article outlines product analysis and positioning, microservice architecture principles, the evolution of real‑time message push technologies, strategies for ensuring request idempotency, and comprehensive service governance practices, providing practical guidelines for building robust backend systems.
This article explains the core challenges of handling massive simultaneous requests and presents a comprehensive high‑concurrency architecture, covering infrastructure deployment, service‑side design, application‑level optimizations, clustering, database sharding, caching layers, message‑queue smoothing, service governance, resource isolation, and practical techniques such as multithreading and coroutine usage.
This article examines the technical challenges of B‑end contract advertising systems, tracing the evolution of Baidu's ad‑placement platform from a monolithic architecture through multiple business stages to a domain‑driven microservices design, and discusses service governance, observability, anti‑corruption, and iterative development practices.
The article examines Baidu's Contract Advertising Platform, detailing its shift from a monolithic, siloed design to a DDD‑driven microservices architecture using COLA, CQRS, and layered governance, and shares best practices for handling complex B2B advertising scenarios, service iteration, and evolving business needs.
This article explains how to achieve comprehensive service governance in a microservice architecture using SpringCloud Alibaba's Nacos and Dubbo, covering service registration and discovery, load balancing, rate limiting and circuit breaking with Sentinel, configuration management, and monitoring with Prometheus and SkyWalking.
This article traces the evolution of internet architecture from monolithic to distributed and microservice models, explains the concepts of serviceization and service governance, and details how Dubbo implements these ideas while highlighting the benefits, challenges, and practical implementation steps for modern backend systems.
This guide explains how to use Alibaba Cloud MSE to perform full‑link gray deployments, monitor traffic with runtime white‑screening, and apply configuration gray releases, providing step‑by‑step instructions, rule definitions, and practical examples for microservice environments.
The article presents a comprehensive overview of Dongfang Securities' enterprise business middle platform, detailing its background, definition, construction principles, user journey, overall architecture, domain‑driven design, technical stack, service governance, PaaS, multi‑active deployment, R&D management, data governance, and the practical outcomes achieved through this cloud‑native transformation.
On August 5, the ITCP Alliance hosted a four‑hour closed‑door technical exchange at ZhaiZhai Group where five member companies shared detailed traffic routing practices, discussed common challenges, and outlined future collaborative initiatives to improve service governance and operational efficiency.
This article outlines the evolution of microservice architecture, the rising need for service governance, and provides a detailed, step‑by‑step guide to planning, organizing, and implementing governance capabilities using Tencent Cloud TSF, including its core concepts, preparation checklist, governance blueprint, and SDK communication mechanisms.
This article explains how Spring Cloud Tencent enables multi‑test environment routing by using service instance tagging, traffic staining, and Polaris‑based service routing, providing step‑by‑step guidance for developers to configure plugins, label instances, and apply request‑level tags for efficient microservice testing.
This article details how a CPaaS team leveraged Alibaba Cloud's MSE to create isolated project environments, enable gray releases, and improve microservice testing and traffic management on Kubernetes, sharing practical steps, architecture diagrams, and future plans.
The article explains common instability scenarios in production, introduces flow control and circuit‑breaker concepts, presents OpenSergo v1alpha1 CRD definitions with concrete YAML examples, and shows how Sentinel and Alibaba Cloud MSE implement these standards to protect microservice systems.
This article examines the motivations, stability and cost considerations, technical challenges, and design principles of a multi‑active hybrid cloud architecture, illustrating how container orchestration, service governance, traffic scheduling, and data storage are coordinated to achieve high availability and cost efficiency across multiple cloud providers.
The article traces Bilibili’s API gateway evolution from a crash‑prone 2015 PHP monolith through a Go‑based bilizone, then fragmented BFF services, to a unified microservice gateway that centralizes routing, authentication, rate limiting, and governance, enabling scalable, decoupled development and a full API ecosystem.
This article examines the inherent complexities of microservice architectures—such as performance, reliability, data consistency, and operational costs—and presents four essential governance approaches, including traffic control, request resilience, self‑protection mechanisms, and fault‑instance handling, to achieve robust high‑availability services.
This article outlines Huolala's journey through five architectural stages—monolith, RPC, SOA, microservices, and service mesh—detailing the motivations, challenges, and technical choices such as Dubbo, Spring Cloud, and Istio that shaped its high‑availability, cloud‑native backend platform.
OpenSergo, launched by Alibaba Cloud, bilibili, ByteDance and major open‑source communities, seeks to create a language‑agnostic, technology‑agnostic service‑governance specification and implementation that unifies control and data planes for heterogeneous microservices, easing enterprise complexity, reducing developer burden, and encouraging open‑source contributions.
This article presents a comprehensive overview of payment system architecture, detailing the transaction and payment cores, their interactions, service governance, data consistency, asynchronous processing, performance testing, and practical production practices for building robust backend payment platforms.
This article traces the evolution of system architecture from monolithic applications through vertical splitting, distributed services and SOA to modern microservices, explaining their advantages, challenges, design principles, governance, observability, automation, and remote‑call mechanisms such as RPC.
After a decade of rapid growth, JD.com’s information system now handles procurement, sales, and inventory across a horizontally and vertically split architecture, tackling challenges of service decoupling, efficient communication, data consistency, and governance, while outlining its vision, principles, implementation details, and stability‑enhancing governance practices.
This article reviews the historical evolution of system architecture—from single‑application monoliths through vertical splitting, distributed services, SOA, and finally microservices—explaining their advantages, drawbacks, design principles, remote‑call mechanisms, automation, monitoring, and the relationship between SOA and microservices.
This article traces the evolution of system architecture—from simple monolithic applications through vertical splitting, distributed services, SOA, and finally microservices—explaining their advantages, drawbacks, design principles, remote‑call mechanisms, and the operational practices needed for modern backend development.
This article outlines essential techniques for building large‑scale backend systems, covering product analysis, microservice architecture principles, the evolution of real‑time push technologies, request idempotency strategies, and comprehensive service governance challenges and solutions.
This article explains service governance concepts, the challenges of managing thousands of micro‑services, introduces etcd and its Raft‑based consistency model, details BoltDB storage internals, and describes Baidu's large‑scale Tianlu platform with its high‑availability, performance, scalability, and operational metrics.
This article recounts a year‑long journey of designing, implementing, and operating a multi‑environment Kubernetes architecture—including containerized workloads, unified logging, CI/CD pipelines, service governance with Istio, and private deployments—while sharing practical lessons and best‑practice recommendations for cloud‑native teams.
The article explains how a Backend‑For‑Frontend (BFF) layer can be constructed using GraphQL for on‑demand data fetching, JSON template engines for data transformation, and routing capabilities for version handling, resulting in a scalable, maintainable architecture that integrates with low‑code front‑end platforms.
This article shares practical experience on designing and operating a high‑concurrency order‑delivery system, covering infrastructure choices, database scaling techniques such as read‑write separation and sharding, architectural patterns like caching, message queues and service governance, as well as application‑level optimizations including compensation, idempotency, async processing and warm‑up strategies.
Modern micro‑service architectures evolve from basic RPC protocols—covering serialization, transport, invocation modes, and governance—into comprehensive service‑oriented frameworks that integrate registration, load balancing, fault tolerance, observability, and automation, with popular open‑source tools like Dubbo, gRPC, and Thrift guiding implementation choices.
This article introduces service governance fundamentals, explains how etcd’s Raft‑based consensus and BoltDB storage work, compares etcd with ZooKeeper and Consul, and describes Baidu’s large‑scale, high‑availability, high‑performance service‑governance platform built on these technologies.
This article provides a comprehensive overview of microservices architecture, covering its definition, comparison with monolithic systems, design principles, communication methods, benefits, drawbacks, governance, and practical considerations such as DevOps, containers, and real‑world case studies.
This article explores service governance fundamentals, examines why etcd’s Raft‑based consensus and BoltDB storage make it ideal for large‑scale systems, compares it with ZooKeeper and Consul, and shares Baidu’s practical architecture, performance tricks, and operational metrics for high‑availability, high‑performance service management.
In this detailed account of Huolala's 2021 Cloud Operations Best Practices talk, the company shares its multi‑cloud architecture, service‑oriented governance, capacity‑testing, monitoring, and risk‑prediction techniques that together ensure high‑availability and efficient scaling for its diverse logistics services.