This article reviews the evolution of service discovery in cloud‑native microservices, comparing Eureka, Consul, Nacos, SLB, Kubernetes Service and Istio, and discusses their architectures, strengths, limitations, and practical considerations for selecting the most suitable solution.
This article explains the origins, core principles, and practical components of Cloud Native—including microservices, containerization, DevOps, continuous delivery, and cloud infrastructure—showing how they reshape development culture, organization, and technology adoption for modern software teams.
This comprehensive guide explains what software architecture is, distinguishes systems, subsystems, modules, components, and frameworks, outlines architecture layers and classifications, describes strategic versus tactical design, tracks the evolution from monoliths to micro‑services, and highlights how to evaluate and avoid common architectural pitfalls.
This article presents a curated list of 29 Alibaba open‑source projects—including Spring Cloud Alibaba, Ant Design, Druid, Fastjson, Dubbo, JStorm, Nacos, Sentinel, and many more—detailing their core purpose, key features, and GitHub repositories for developers seeking robust solutions across cloud, micro‑services, frontend, and data processing domains.
This article outlines the step‑by‑step evolution of a high‑traffic e‑commerce backend—from a single‑machine setup through caching, load balancing, database sharding, microservices, containerization, and finally cloud deployment—while summarizing the key technologies and design principles at each stage.
The article introduces Tars, a high‑performance RPC framework and integrated service governance platform that leverages micro‑service architecture, detailing its design philosophy, layered architecture, key features such as the Tars protocol, load balancing, fault tolerance, overload protection, configuration management, and open‑source availability.
This article explains how service discovery has progressed from simple centralized proxies to client‑embedded libraries and finally to host‑level independent processes like Service Mesh, detailing each generation, their pros and cons, and how Kubernetes implements discovery and load balancing.
Microservice architecture blends SOA, componentization, and domain modeling, and today a variety of open‑source frameworks—such as Spring Cloud, Eclipse MicroProfile, Dubbo, Tars, Helidon, SOFAStack, gRPC, Thrift, and brpc—along with leading Service Mesh solutions like Linkerd, Envoy, Istio, and Conduit, empower developers to build scalable, cloud‑native applications.
This article explains the fundamental concepts of software architecture, distinguishes systems, subsystems, modules and components, describes various architectural layers such as business, application, data, code, technical and deployment, outlines evolution from monoliths to micro‑services, and highlights common misconceptions and measurement criteria for a sound architecture.
This article explains how to construct a PaaS cloud platform using microservice architecture, Docker containers, and Spring Cloud components such as Zuul, Eureka, and Hystrix, covering service gateway, registration, fault tolerance, and dynamic configuration to enable rapid development and deployment.
This article explains why microservice calls need fault‑tolerance mechanisms, introduces Hystrix’s core features such as timeouts, circuit‑breaker, fallback, monitoring and resource isolation, and provides step‑by‑step code examples for integrating Hystrix and Feign in a Spring Cloud project.
Microservices aren’t a universal solution; this article outlines five common situations—insufficient complexity, small teams, indivisible applications, legacy system integration, and tight real‑time integration—where adopting a microservice architecture can add unnecessary overhead and risk, advising developers to choose the right architecture for their needs.
Before defaulting to a microservices architecture, developers should evaluate whether their application is large enough, truly needs component scaling, can handle cross-service transactions, and can tolerate increased latency and complexity, as these factors determine if microservices will add value or unnecessary overhead.
This article compares three seasoned experts' approaches to microservice splitting—vertical vs. horizontal, business‑driven, stability‑driven, and performance‑driven—highlighting trade‑offs, team size considerations, and practical guidelines for achieving scalable, maintainable architectures.
This article presents a structured approach to mastering microservices, covering a learning pyramid, a step‑by‑step roadmap, weekly ARTS habits, and detailed explanations of the six essential components that together form a robust microservice architecture.
This article explores the fundamentals of monolithic and microservice architectures, assesses the benefits, costs, and risks of adopting microservices, and provides practical criteria—including business complexity, team size, and technical readiness—to help decide the optimal moment for migration.
In large‑scale microservice environments, centralized log collection, filtering, and visualization using Filebeat, Elastic APM, Kafka Streams, Grafana and Prometheus can turn scattered logs into actionable operational data while controlling resource costs.
This article explains the fundamentals of distributed systems, covering the CAP and BASE theorems, caching strategies, message queues, database choices, JVM optimization, and practical architectural improvements applied to New Oriental's mobile app to enhance availability and performance.
This article explains the concept, states, and practical benefits of circuit breaker mechanisms in microservice architectures, illustrating how they prevent cascading failures, improve system stability, and provide configurable recovery strategies for robust cloud‑native applications.
This article details Saike Mobility's successful Level‑3 DevOps continuous‑delivery assessment, shares insights from an interview with their operations director, and explains the national DevOps capability maturity model that is shaping engineering efficiency across Chinese tech enterprises.
This article explains what GraphQL is, how its type system and Relay standard work, the N+1 problem, and presents three architectural approaches—prefixing, schema stitching, and RPC composition—for integrating GraphQL into microservices, along with authentication, authorization, and routing considerations.
Xianyu’s zero‑downtime upgrade strategy for its multi‑microservice search stack combines rigorous forward/backward compatibility checks, batch‑wise stateless updates, careful stateful migrations via hot‑updates or dual‑write sync, robust service‑discovery traffic control, and Alibaba‑style monitoring, gray‑release testing, and rapid rollback to ensure uninterrupted service.
This article explains how to construct a reliable, high‑throughput microservice platform using open‑source components such as Consul, an access layer, and token‑based multi‑tenant service discovery, covering architecture, registration, heartbeat handling, performance optimizations, high‑availability strategies, graceful shutdown, and deployment best practices.
This guide explains how to download, build, and run Nacos from source, customize its UI, ensure server‑client version consistency, and modify configuration files, providing step‑by‑step commands and code snippets for Linux, macOS, and Windows environments.
This article explains how to design a non‑intrusive distributed tracing system for microservices by assigning global TraceIDs, generating hierarchical SpanIDs, using lightweight agents to propagate identifiers via transport headers, and aggregating data in a collector to visualize complete call graphs and diagnose performance issues.
This article explores how Nginx’s high‑performance, event‑driven architecture underpins modern DevOps practices, detailing its roles in web hosting, proxying, caching, API gateways, dynamic routing with Lua/Redis, emergency failover designs, data‑driven operations, and micro‑service integration.
This article explains how Sentinel Go provides flow control, warm‑up throttling, concurrency limiting, circuit breaking, hotspot protection, and system‑adaptive safeguards to keep distributed microservices stable under traffic spikes, third‑party failures, and resource contention.
This article analyzes Beike's massive real‑estate ecosystem, detailing the intricate business flows, technical architecture, and quality‑assurance challenges, and explains how a suite of internal platforms—KeTest, KeOnes, sosotest, KeDiff, KePTS, and KeMTC—are engineered to deliver high‑performance, highly available services at scale.
The article introduces Tars, an open‑source high‑performance RPC framework and integrated service governance platform derived from Tencent's internal microservice architecture, detailing its design philosophy, layered architecture, core features such as the Tars protocol, load balancing, fault and overload protection, and centralized configuration management.
This article details a four‑layer cloud‑native system architecture that separates presentation, communication, service, and data layers, leveraging Spring Cloud microservices, Alibaba Cloud networking, multiple databases, JWT authentication, ELK logging, and HTTP DNS to achieve scalability, reliability, and optimal user experience across web, app, and IoT platforms.
The article introduces eight widely used software architecture design patterns—including single‑database single‑application, content distribution, query separation, microservice, multi‑level cache, sharding, elastic scaling, and multi‑datacenter—explaining their typical structures, suitable scenarios, and the main pros and cons of each.
This article provides a comprehensive overview of Spring Cloud's core modules—including service discovery with Eureka, client‑side load balancing via Ribbon, declarative REST calls with OpenFeign, fault tolerance using Hystrix, API gateway features of Zuul, centralized configuration with Config, and dynamic refresh through Spring Cloud Bus—illustrated with diagrams and code examples.
This article examines Eastern Securities' transition to a microservice architecture by detailing the design, implementation, and performance of its gRPC‑Nebula service‑governance framework and the Star‑Chen platform, covering challenges such as heterogeneous interfaces, service registration, load balancing, fault tolerance, traffic control, multi‑registry support, and real‑world deployment results.
This article walks through the evolution of an online supermarket from a simple monolithic web application to a fully decomposed microservice architecture, highlighting the challenges of scaling, the need for monitoring, tracing, service discovery, fault tolerance, and the eventual adoption of a service mesh.
This article describes the design, architecture, and innovations of a custom API gateway for microservice systems, covering technical selection, protocol conversion for Dubbo, service orchestration, embedded gateway deployment, high‑availability strategies, and measurable efficiency gains.
This article explains the fundamentals of distributed tracing, the OpenTracing standard, and how SkyWalking implements automatic span collection, cross‑process context propagation, unique traceId generation, sampling strategies, performance benchmarks, and real‑world adaptations within a micro‑service environment.
This article details CTrip's journey from its early .Net‑based ESB architecture through a self‑developed Java microservice framework to the current CDubbo platform, covering registration, monitoring, dynamic configuration, protocol compatibility, performance gains, extensibility, and future Service Mesh integration.
Tencent Cloud API 3.0 introduces a unified, secure, high‑performance API Gateway that centralizes access, routing, and lifecycle management for microservices, offering standardized interfaces, multi‑language SDKs, CLI and Explorer tools, precise rate limiting, rich documentation, and a roadmap toward industry‑wide standardization and broader scenario adoption.
The article reviews the design and implementation of 58.com’s intelligent voice robot backend, detailing its four‑layer architecture, SIP/SDP/RTP protocols, multi‑round voice interaction flow, algorithm service modularization, SIP scheduling optimizations, and Java thread‑pool system tuning for high‑concurrency scenarios.
This article surveys the rise of microservices and presents a comprehensive list of widely used Java, .NET, Node.js, Go, and Python frameworks, highlighting their features, adoption statistics, and suitability for building scalable, loosely‑coupled backend systems.
This article explains how to design and implement service‑chain (APM) monitoring and end‑to‑end process monitoring in distributed systems, covering concepts such as spans and traces, TRACE_ID generation, logging practices, visualisation techniques, and a practical expense‑report use case with code examples.
The article explains the challenges of API version control, introduces canary release as an alternative deployment strategy, and illustrates its practical implementation at ING Bank, highlighting benefits such as gradual rollout, easy rollback, and improved stability for continuously evolving APIs.
The article chronicles the evolution of the open‑source Java e‑commerce project “mall”, detailing its rise from 20K to over 40K GitHub stars, the transition to microservices with Spring Cloud, deployment enhancements, auxiliary tools like Docker, Jenkins and MinIO, and future ecosystem plans.
The article explains what cloud‑native applications are, contrasts them with traditional software, outlines four core cloud‑native development principles, and details a six‑step process—including DevOps culture, lightweight servers, PaaS, framework selection, automation, and modular architecture—to accelerate building and deploying cloud‑native solutions.
This article analyzes the challenges of tightly coupled microservices and presents practical decoupling techniques—including asynchronous messaging, event‑driven architecture, CQRS, local caching, and service refactoring—to improve resilience and availability in modern backend systems.
This article compares five common software architecture patterns—layered, event‑driven, microkernel‑plugin, microservices, and cache—detailing their structures, advantages, drawbacks, and ideal use cases, helping architects choose the most suitable design for new or existing applications.
Zeebe is an open‑source workflow engine that enables visibility, fault‑tolerance and horizontal scalability for end‑to‑end microservice workflows, offering BPMN‑based modeling, append‑only log storage, and language‑agnostic client libraries to orchestrate and monitor complex business processes.
This article describes the design and implementation of a PaaS cloud platform based on microservice architecture, covering service access paths, gateway functions with Zuul, service registration with Eureka, fault tolerance using Hystrix, dynamic configuration via Spring Cloud ConfigServer, and Docker container deployment.
The article presents Hmily’s monthly report, detailing its high‑performance distributed transaction solution, recent architectural refactoring, newly added modules and SPI implementations, community‑driven bug fixes and feature releases, and outlines upcoming versions supporting TCC and TAC modes.
This article outlines a comprehensive backend technology selection guide for microservices, covering programming languages, IDEs, frameworks, RPC solutions, distributed transaction tools, API gateways, configuration centers, service discovery, monitoring, logging, database middleware, serialization, build tools, containers, orchestration, and runtime environments.
This article explains the principles, advantages, and step-by-step process of component-based development, covering business modeling, software requirements, system and technical design, implementation, and integration within modern microservice and SOA architectures.
This article provides a comprehensive overview of Spring Cloud's core modules—including service discovery with Eureka, client‑side load balancing via Ribbon and Feign, API gateway functionality of Zuul, fault‑tolerance with Hystrix, and centralized configuration management with Config—illustrated through a typical e‑commerce order‑payment scenario and comparisons with Dubbo, Zookeeper, and Nginx.
This article discusses how to reduce coupling between microservices by converting synchronous calls to asynchronous messaging, employing message middleware, event‑driven architecture, CQRS patterns, local caching, data landing, and refactoring techniques such as merging services, extracting common modules, and adjusting granularity.
This article presents the background, core features, system architecture, internal mechanisms, and practical extensions of ZZSCHEDULE, a distributed task scheduling platform built on the open‑source XXL‑JOB framework, detailing its design goals, HA strategies, task dependency handling, and deployment experiences at Zhuanzhuan.
This article explains how latency is used as a key indicator for application risk identification, defines slow interfaces, describes why percentile‑based thresholds are preferred over averages, and outlines the architecture, task workflow, and practical optimization strategies for a full‑chain monitoring system in a microservice environment.
The article outlines how open x86 hardware, solid‑state storage, high‑speed networking, resource pools and containers form the foundation for modern IT architecture, while national emphasis on innovation and security elevates open‑source software, driving a shift toward layered, service‑oriented, microservice‑centric systems integrated with DevOps pipelines.
This article examines the transition from monolithic to microservice architecture, outlining the benefits and drawbacks of each, the conditions under which microservices should be adopted, the necessary technical and team resources, risk assessments, and practical guidance on service decomposition and migration.
iQIYI’s contract platform replaced a cumbersome Activiti workflow with a lightweight combination of Axon Framework and Spring StateMachine, leveraging DDD, CQRS, and event sourcing to achieve clear layered architecture, traceable events, and flexible state transitions, while confronting distributed‑transaction sagas, batch limits, and integration complexities, and planning future Axon Server adoption.
This article explains the fundamental concepts of software architecture, including definitions of systems, modules, frameworks, various architectural layers such as business, application, data, code, technical and deployment, and discusses the evolution from monolithic to distributed and microservice architectures along with evaluation criteria and common pitfalls.
This article explains the fundamental concepts of software architecture, distinguishes system, subsystem, module, component, and framework, outlines architectural layers and classifications, describes the evolution from monolithic to distributed and micro‑service architectures, and discusses how to evaluate and avoid common design pitfalls.
This article details iQIYI's adoption of Apache Dubbo for microservice architecture, covering its history, SDK extensions such as health‑check isolation, region‑aware routing, authentication, protobuf support, the evolution of their service registry to Nacos, monitoring built on Prometheus and Sentinel, and outlines future cloud‑native and service‑mesh initiatives.
The article explains microservice fundamentals, the challenges of client‑to‑service communication, and how API gateways, Backend‑for‑Frontend patterns, and Service Meshes address these issues while outlining key gateway features, popular implementations, and selection criteria for robust backend architectures.
This article explains how to treat Domain‑Driven Design as code by leveraging ContextMapper's DSL to model strategic and tactical aspects, define subdomains, bounded contexts, context maps, and generate consistent documentation and code artifacts for microservice architectures.
Microservice architectures struggle with traditional ACID transactions, so this article reviews local and distributed transaction basics, explains why 2PC/3PC are unsuitable, introduces the BASE model, and details four practical consistency patterns—reliable event, async event, business compensation, and TCC—highlighting their mechanisms, advantages, and drawbacks.
From early .Net ESB attempts to a Java‑based CDubbo framework, CTrip details its migration to Dubbo, covering registration, health checks, CAT monitoring, dynamic configuration, SOA compatibility, testing tools, thread‑less execution, performance gains, extensibility, ecosystem integration, and future service‑mesh standardization.
The article explains, through interview excerpts, why many game studios avoid microservice architectures for their real‑time servers, highlighting latency‑sensitive communication, stateful processing, and the overhead of distributed networking that conflict with the performance demands of modern multiplayer games.
The article explains the fundamentals of distributed architecture, its high‑availability mechanisms, scalability benefits, common pitfalls such as data consistency, and real‑world case studies ranging from e‑commerce platforms to Nginx reverse proxy and microservice designs.
This article explains how microservices have evolved from monolithic applications to cloud‑native environments, covering lifecycle management, traffic governance, programming models, trusted security, the role of containers, service mesh, Dapr, and Alibaba Cloud's EDAS platform, while highlighting active open‑source projects.
This article walks through the transformation of a simple online supermarket from a monolithic design to a fully fledged microservice system, explaining the motivations, architectural changes, component selection, common pitfalls, and best‑practice solutions such as service decomposition, database sharding, monitoring, tracing, service mesh, resilience patterns, and testing strategies.
This article explains the concept of microservices, how they communicate via synchronous RPC or asynchronous messaging, compares Spring Cloud with Dubbo, clarifies the relationship between SpringBoot and SpringCloud, and discusses circuit breaking, service degradation, pros and cons, Eureka vs Zookeeper, and a typical technology stack.
The article explains why large distributed applications quickly become complex, identifies cognitive‑load and collaboration‑cost as the two key dimensions of software complexity, analyses concrete causes such as poor logic, mismatched models, bad API design, naming and testing gaps, and offers practical principles for keeping complexity under control.
This article explores why massive distributed applications quickly become complex, identifies cognitive load and collaboration cost as the two main dimensions of software complexity, and offers practical design, naming, testing, and documentation strategies to keep systems maintainable over time.
This article introduces Spring Cloud as a Spring Boot‑based microservice framework, explains the fundamentals of service architecture through an illustrative story, and details essential components such as service registry, discovery, load balancing, circuit breaking, configuration management, messaging bus, and tracing, accompanied by practical code examples.
This article explains why abrupt service restarts cause "Can not get connection to server" errors in Zookeeper‑based microservices and details a Java ShutdownHook solution that deregisters instances, processes in‑flight requests, and prevents client‑side failures during graceful shutdown.
Sentinel 1.8.0 introduces extensive flow‑control, circuit‑breaker, and degradation improvements for microservices, adds native support for Java EE, Quarkus, and HTTP clients, and resolves critical bugs, making it a pivotal release for high‑availability distributed systems.
Effective API design in microservices requires platform independence, reliability, appropriate RESTful maturity, avoiding simple wrappers, ensuring separation of concerns, exhaustive and independent endpoints, proper versioning, consistent naming, and security measures, all of which are detailed alongside practical examples and a comprehensive review checklist.
This article chronicles Yuque's evolution from a low‑cost prototype built on internal BaaS services to a fully commercialized, cloud‑native knowledge platform, highlighting the shift to IaaS, micro‑services, and serverless function compute to improve scalability, stability, security, and cost efficiency.
This article chronicles Yuque's evolution from a hobbyist prototype to a commercial cloud‑native knowledge platform, detailing its backend migrations, adoption of Node.js, Egg, React, serverless function compute, micro‑service splits, and the architectural lessons learned for stability, cost efficiency, and scalability.
This article examines why many game companies avoid microservice architectures, highlighting the real‑time latency, stateful memory requirements, and networking constraints that make traditional microservice patterns unsuitable for fast, multiplayer game servers.
This article provides a comprehensive overview of Kubernetes, explaining its master‑node architecture, core components, deployment workflow, pod fundamentals, scaling and update strategies, networking layers, and service discovery mechanisms, enabling readers to grasp how container orchestration works in practice.
This article explains how cloud‑native principles—combining agile, DevOps, CI/CD, microservices, service governance, container technology, and cloud computing—address modern application challenges such as rapid deployment, elastic scaling, fault detection, self‑healing, and alignment with organizational structures.
This article introduces RabbitMQ’s core concepts, explains message reliability features, and demonstrates a practical order‑creation scenario with Java code that publishes messages, consumes them for score updates and notifications, and shows the resulting output.
This article explains how business architecture controls system complexity through layered structures and domain‑driven design, compares traditional three‑tier and microservice architectures, highlights common pitfalls, and offers a lightweight domain‑centric approach for scalable, maintainable backend systems.
This article details how the Alibaba Nacos service registry was evaluated and chosen over Eureka, Zookeeper, and Consul for a large‑scale micro‑service platform, presenting comprehensive performance benchmarks, functional API tests, sync behavior analysis, and automated JUnit testing with real‑world deployment data.
This article compares monolithic applications and microservice architectures across dimensions such as network latency, development and operational complexity, reliability, resource consumption, scaling precision, throughput, deployment speed, and team communication, highlighting where each approach wins and offering guidance on when to adopt microservices.
This article examines the motivations, resource granularity, rule definition, and calculation logic behind implementing rate limiting and circuit breaking in microservice architectures, using examples like Sentinel and Hystrix, and outlines a step-by-step design for integrating these controls with API gateways.
Game servers often avoid microservice architectures because real‑time communication, low latency, and stateful processing demand tightly coupled, high‑performance designs, making the added network overhead, stateless constraints, and complexity of microservices unsuitable for fast‑paced multiplayer games.
This article explains what microservices are, how they communicate, compares Spring Cloud with Dubbo, describes the relationship between Spring Boot and Spring Cloud, and discusses circuit breaking, service degradation, advantages, disadvantages, service discovery tools, and typical technology stacks.
This article reviews fifteen leading open-source API management platforms, outlining their key features such as rate limiting, authentication, analytics, and developer portals, to help developers and architects choose the most suitable solution for modern backend and micro‑service environments.
This article surveys fifteen leading open‑source API management platforms—such as API Umbrella, Gravitee.io, Kong Enterprise, and 3Scale—detailing their key features like rate limiting, authentication, analytics, and developer portals, to help backend teams choose the right solution for their microservice architectures.
This article examines Netflix’s cloud‑based microservices architecture, detailing its client, backend, CDN components, design goals such as high availability, low latency, scalability, and the trade‑offs, resilience mechanisms, and scalability strategies employed on AWS to support millions of global streaming users.
The article uses a thought experiment of a computer left idle for a year to illustrate how software architecture must evolve from static diagrams to operationalized, continuously delivered microservices, emphasizing the importance of DevOps, feature toggles, and real‑world resilience.
This article evaluates popular Java microservice frameworks—Spring Boot, Micronaut, Quarkus, and Helidon MP—by measuring their ease of development, compilation time, startup latency, memory usage, and high‑load request handling, using identical CRUD applications deployed on Docker and GraalVM.
The article examines why tightly coupled microservices cause reliability issues, then presents practical techniques—such as converting synchronous calls to asynchronous messaging, adopting event‑driven architecture, using CQRS, caching, and strategic refactoring—to achieve loose coupling and improve system resilience.
This article explains the concept of Service Mesh, why it emerged from micro‑service challenges, its evolution, and compares the main open‑source implementations such as Linkerd, Envoy, Istio, and Conduit, helping readers grasp its role in modern cloud‑native architectures.
This guide explains practical techniques—service splitting, caching, message queues, database sharding, read/write separation, and Elasticsearch—to design high‑concurrency back‑end systems that impress interviewers and handle real‑world traffic spikes.
This article explains why Medium transitioned from a monolithic Node.js application to a microservice architecture, outlines the three core design principles, shares practical strategies for building and operating services, and warns about common pitfalls such as the microservice syndrome.
iQIYI built a Prometheus‑based microservice monitoring platform that uses Spring Boot Actuator, Micrometer, custom QAE collectors, file‑based service discovery, and an Alert‑proxy to gather container, application, and third‑party metrics, define PromQL alert rules, and forward alerts to its unified notification system, illustrating best practices and lessons learned.
To address the challenges of managing logs across hundreds of microservices in production, the article presents an enterprise log monitoring solution that centralizes collection via Filebeat, processes logs with Kafka Streams, visualizes data using Grafana and Kibana, and integrates Elastic APM for tracing and performance metrics.
Learn to unify API documentation across multiple Spring Cloud microservices by configuring Nacos, Spring Cloud Gateway, and Knife4j, covering prerequisite setup, service definitions, detailed implementation steps, Swagger resource aggregation, UI switching, and complete code examples for user, order, and gateway services.
