This article provides a comprehensive technical guide on using Kubernetes and OpenShift for container‑cloud deployment, covering architecture, multi‑tenant isolation, security, load balancing, logging, monitoring, CI/CD, storage options, and best practices especially for financial‑industry microservice workloads.
This tutorial walks through the fundamentals of distributed systems—explaining clusters, distributed architecture, the CAP theorem, and then dives deep into Spring Cloud components such as Eureka, Ribbon, Hystrix, Feign, Zuul, and Config, illustrating how they solve real‑world microservice challenges.
The article examines the advantages and disadvantages of microservice architectures, discussing flexibility, scalability, autonomy, monitoring, build and release complexity, security, and data replication, while highlighting practical trade‑offs and lessons learned from real‑world implementations.
This article explains how shifting from synchronous command‑driven interactions to asynchronous event‑driven flows reduces coupling, improves scalability, and enables flexible querying in distributed systems, while also discussing hybrid patterns, the single‑writer principle, and practical advantages illustrated with Kafka‑based examples.
The article reviews the evolution of Service Mesh and Dubbo, compares sidecar and SDK deployment models, discusses key technical challenges such as multi‑language support, performance, and operations, and explains how Dubbo integrates with Kubernetes to enable cloud‑native micro‑service architectures.
This article explains the shortcomings of traditional configuration files, describes why distributed configuration centers are essential for dynamic, multi‑environment microservice deployments, outlines their evolution, presents a simple design with caching and consistency improvements, and reviews popular open‑source solutions.
This article details the late-stage refactoring of Ctrip's SEO system, explaining why the overhaul was needed, the backend technology stack choices, the modular architecture—including data collection, processing, and service layers—and the performance optimizations implemented to support large‑scale search‑engine‑driven traffic.
This article explains what RPC is, compares it with SOA, SOAP, and REST, outlines the step‑by‑step RPC execution process, and introduces several mainstream RPC frameworks such as RMI, Hessian, protobuf‑rpc‑pro, Thrift, Avro, and Dubbo.
The iQIYI video backend team outlines their microservice journey, detailing service decomposition strategies, choosing Spring Cloud for its low migration cost and rich ecosystem, and building a shared platform of registries, configuration, gateways, monitoring, and CI/CD to boost efficiency, reliability, and scalability while planning future adoption of service mesh and domain‑driven design.
This document presents a comprehensive solution for merchant settlement in joint‑venture (co‑operated) offline stores, describing business models, settlement subject abstraction, billing engine components, settlement workflow, payment collection, and reconciliation architecture with detailed tables and diagrams.
This article explains the principles and operation of circuit breakers and retry mechanisms in microservice architectures, describes their three states, key configuration parameters, demonstrates a Hystrix‑Go implementation, and discusses back‑off strategies and the combined use of both techniques for resilient backend services.
Distributed transactions ensure atomicity across services, and RocketMQ provides a half-message mechanism with a two-phase commit and a rollback check that lets producers and consumers coordinate transaction steps reliably even when confirmations are delayed.
Microservices decompose applications into small, autonomous services, offering advantages such as independent deployment, scalability, and technology diversity, while introducing challenges like operational complexity, DevOps demands, and governance, and the article compares them to monolithic architectures, discusses communication patterns, API design, and supporting infrastructure.
This article examines the shortcomings of decentralized and micro‑service‑only approaches for enterprise integration, argues for version‑less services, explains how a centralized ESB and multi‑center architecture can balance security, efficiency, and scalability, and outlines practical design patterns and component roles.
This article presents a curated collection of outstanding Spring Cloud open‑source projects, describing their purpose, key features, and providing direct GitHub links to help developers quickly adopt microservice solutions and related tools in Java‑based cloud‑native environments.
This article curates twelve high‑quality Spring Cloud open‑source projects—ranging from service discovery and configuration to monitoring, circuit breaking, and payment integration—providing concise descriptions and direct GitHub links to help developers quickly adopt robust microservice solutions.
This article compares the three major container orchestration platforms—Kubernetes, Docker Swarm, and Amazon ECS—examining their architecture, integration with cloud providers, deployment complexity, and suitability for different workloads to help readers choose the right tool for their needs.
This article explains microservice architecture, contrasting it with monolithic systems, outlines its benefits, challenges, governance, communication patterns, and the role of containers and DevOps in enabling fast, low‑cost responses to change.
This article explains why UCloud introduced a Service Mesh, how Istio was chosen and adapted for the UAEK Kubernetes platform—including IPv6 challenges, performance testing, and future improvements—providing practical insights for building reliable micro‑service infrastructures.
This article provides a comprehensive introduction to Docker, covering its open‑source origins, client‑server architecture, networking and storage solutions, integration with PaaS/IaaS platforms, impact on DevOps practices, and its pivotal role in enabling modern microservice architectures.
This article explores practical Domain‑Driven Design in a B‑to‑B setting, comparing data‑centric and object‑centric modeling, illustrating blood‑loss, anemia, and rich models, and showing how dependency injection, testing strategies, repository abstractions, and deployment architectures can improve software quality and maintainability.
The article explains the concept of service isolation, its origins in shipbuilding, why it’s crucial for reducing fault impact in software systems, practical approaches such as functional and user‑based isolation, their trade‑offs, and key design principles to ensure reliable, maintainable back‑end architectures.
The article describes how 58's search technology team standardized and modularized their vertical search services into a cloud-native platform, detailing the overall architecture, Kubernetes‑based deployment, service and deployment designs, stateful indexing challenges, and solutions for high‑availability and scalability.
This article outlines the progressive evolution of large-scale internet architectures, detailing the transition from simple monolithic designs through clustering, caching, read/write separation, static/dynamic separation, high‑availability clusters, distributed systems, SOA, microservices, and finally service mesh, highlighting their principles, benefits, and challenges.
This article outlines the step‑by‑step evolution of a Java web e‑commerce platform, covering initial single‑machine deployment, server‑database separation, application clustering, load‑balancing algorithms, session handling, read‑write splitting, caching, database sharding, microservice decomposition, and the introduction of messaging middleware to achieve a scalable, resilient architecture.
This article reviews the essential Spring Cloud microservice stack for enterprise use, covering core gateway, service discovery, configuration, security, monitoring, tracing, and alerting components, and explains why tools like Apollo, Consul, Kafka, ELK, Pinpoint, InfluxDB, and Prometheus are preferred in production environments.
This article outlines ten crucial design principles for building robust microservice systems, covering API gateways, stateless services, database scaling, caching, service splitting, orchestration, configuration management, logging, resilience patterns, and comprehensive monitoring to ensure high performance and reliability.
This article explains how to integrate spring-cloud-zuul-ratelimit with Zuul for distributed rate limiting, covering supported granularity levels, storage back‑ends, YAML configuration examples, custom key generators, and practical demonstration using Redis and Spring Boot Actuator.
This article shares practical guidance on designing, protecting, and continuously improving high‑concurrency backend services—covering baseline capacity, rate limiting, data‑structure optimization, stateless architecture, and horizontal scaling—to help engineers evolve small systems into robust, production‑grade platforms.
This article provides a comprehensive overview of Spring Cloud, explaining why it’s favored for microservice development, detailing its key features and toolset, and examining essential components such as Eureka, Hystrix, Config, Zuul, and Ribbon with practical insights.
This article provides a comprehensive technical overview of Ant Financial’s Service Mesh data‑plane SOFAMosn, covering its architectural background, layered design, core modules, performance optimizations, supported protocols, and future roadmap within a cloud‑native microservices ecosystem.
This article presents a curated knowledge map covering backend architecture, Java best practices, microservice design, distributed consistency, high‑traffic handling, Alibaba frameworks, and design patterns, offering internet high‑concurrency architects a comprehensive reference of essential concepts and skills.
This article explains the fundamentals of microservices, contrasts them with monolithic architectures, outlines the pros and cons of each approach, and highlights key characteristics, benefits, and challenges of adopting a microservice‑based backend design.
The author reflects on a four‑year journey of refactoring a complex system into a lightweight, service‑oriented architecture, emphasizing how breaking down monolithic deployments, adopting modular services, and enforcing disciplined conventions can restore simplicity, flexibility, and efficiency in backend development.
Over six years the author chronicles the evolution of a backend system—from its initial three‑day launch, through successive capacity expansions, distributed refactoring, and micro‑service architecture—highlighting the challenges of scaling to millions of users, handling concurrency, and the continuous pursuit of simplicity and resilience.
Istio 1.0, released on August 1, brings the first production‑ready service‑mesh platform with major enhancements in networking, policy & telemetry, out‑of‑process adapters, and security features such as mTLS and JWT, while introducing the IstioGateway to replace the legacy Ingress model.
This article provides a comprehensive guide to over 100 Eureka configuration options, covering client settings, instance microservice parameters, and server configurations, helping developers understand default values, customize behavior, and effectively manage service discovery in Spring Cloud environments.
This article explains Kong’s architecture, core components, key features, plugin ecosystem, request processing flow, and limitations, showing how it provides a high‑availability, horizontally‑scalable API gateway built on OpenResty for modern backend services.
This article outlines six fundamental microservice design patterns—Aggregator, Proxy, Chain, Branch, Data‑Sharing, and Asynchronous Messaging—explaining their structures, use‑cases, scalability characteristics, and potential pitfalls to help architects choose the right approach for their systems.
This article explains why growing business complexity and throughput demand system decoupling, outlines horizontal scaling, vertical and business splitting, database sharding techniques, and shows how architectural evolution leads to micro‑service‑based, resilient infrastructures.
This guide introduces the open‑source SCCA project that adds a visual management layer to Spring Cloud Config, explains its architecture, multiple deployment modes, detailed configuration for Git and DB storage, service‑discovery integration, and provides step‑by‑step instructions for building and using the REST and UI modules in Spring Boot applications.
Pirate Middleware introduces a JSON‑based DSL that orchestrates generic service calls across Meituan’s myriad business lines, replacing heavyweight custom adapters with a decoupled, parallel‑or‑sequential execution engine, thereby shifting data preparation to business teams, cutting development effort, and enhancing reuse, monitoring, and overall platform efficiency.
Meituan Delivery’s architecture has progressed from a rapid MVP with coarse services to a scalable, fine‑grained platform comprising fulfillment, operation, and master‑data subsystems, employing reliability engineering, capacity planning, AI‑driven simulation, and location services to ensure high availability, efficiency, and future‑ready scalability.
This guide compiles resources and key concepts on OpenResty, Lua‑based Nginx development, asynchronous programming models, microservice API gateways, and related plugins, providing a structured roadmap for backend engineers to deepen their understanding and practical skills.
This article outlines ten crucial design principles for building robust microservice systems, covering API gateways, stateless services, database scaling, caching strategies, service decomposition, orchestration, configuration management, logging, fault tolerance, and comprehensive monitoring, each illustrated with clear diagrams.
In a detailed Q&A session at ArchSummit 2018, Ant Financial and Alibaba UC experts discuss the fundamentals, challenges, implementation strategies, and future directions of Service Mesh and Kubernetes, covering performance, multi‑language support, open‑source efforts, and practical advice for developers and operators.
After three years of developing a HR SaaS product, the author recounts the backend’s architectural evolution—from an initial Django MVC prototype, through service splitting, to a microservices setup with Kong API gateway and custom RPC, and finally towards domain‑driven design—highlighting challenges, optimizations, and lessons learned.
This article examines evolutionary architecture for microservices, outlines popular patterns such as CI/CD and the Strangler approach, explains layered and bounded‑context designs, and provides a detailed case study showing how a legacy monolithic system can be incrementally refactored into a flexible, cloud‑native microservice ecosystem.
This article explains how Java‑based microservices can keep data handling manageable by using domain‑driven design, separate data stores, hybrid persistence, event‑driven communication, JPA, EJB, Bean Validation, CDI, and various messaging protocols to achieve consistency and scalability.
This article explains how microservices use service registries for discovery, registration, health checks, and deregistration, compares third‑party and self‑registration, explores server‑side and client‑side call mechanisms, discusses API gateways, synchronous vs asynchronous messaging, and outlines fault‑tolerance patterns such as timeouts, circuit breakers, and bulkheads.
This article explains how to identify, design, and implement Java microservices—from domain‑driven modeling and service boundaries to RESTful API creation, documentation, proper HTTP verbs, and versioning strategies—using examples like an online retail store and the Game On! text adventure.
This article explains the core concepts, characteristics, and advantages of microservice architecture, compares it with monolithic systems, outlines stakeholder benefits, discusses cloud‑native tooling, and provides a practical migration roadmap for Java‑based applications.
The article traces the evolution from early Service‑Oriented Architecture and monolithic applications to modern microservice architectures, highlighting their limitations, the rise of containers and Docker, and how these technologies enable scalable, language‑agnostic, and cloud‑native deployments for complex systems such as e‑commerce platforms.
The article outlines ten major challenges faced when adopting microservice architecture—such as data synchronization, security, version control, discovery, data expiration, debugging, testing, monitoring, DevOps support, and fault tolerance—and presents practical solutions using cloud‑native tools and patterns.
This article explains why microservice architectures demand specialized automated testing, compares testing styles such as unit, contract, and end‑to‑end, and walks through a practical Java‑based framework built on Spring, TestNG and Dubbo, including setup steps and code examples.
This article explains the evolution from a single‑system e‑commerce application to vertically split and SOA‑based distributed architectures, demonstrates how to expose and consume services using Dubbo with complete Java interface and implementation code, and provides configuration, deployment, and testing guidance for both providers and consumers.
This article walks through upgrading Consul to 1.2, configuring service‑mesh support, building two Go micro‑services, registering them with Consul, reloading the configuration, testing the mesh with curl, and provides a detailed analysis of Consul’s service‑mesh architecture, advantages, and limitations.
The article explains how microservice architectures increase testing complexity and presents practical strategies—including orchestration testing, service virtualization, handling API changes, asynchronous command patterns, event firehose, and CI/CD environment configuration—to reliably test individual services and their interactions in cloud‑native environments.
This article explains the core concepts of microservice architecture, outlines its components and pros‑and‑cons, and uses Uber's evolution from a monolithic system to a distributed microservice platform as a detailed case study.
This article outlines the fundamental backend components, frameworks, and services—including API gateways, authentication centers, configuration management, service governance, scheduling, logging, data pipelines, and monitoring—required to build robust, scalable Java business applications for both online and internal use.
This article explores the evolution from Service‑Oriented Architecture to microservices, explaining why microservices succeed, how they differ from traditional monolithic designs, and the practical considerations for adopting them in large‑scale systems.
This article records and translates the first Service Mesher community meetup where Ant Financial’s Service Mesh evangelist Ao Xiaojian presented the exploration of Service Mesh for large‑scale microservice architectures, covering technical selection, architecture design, open‑source strategy, and community resources.
This article explores the evolution and core concepts of modern distributed architectures—including SOA, microservices, and service mesh—explains key theories such as CAP and BASE, and provides practical guidelines for achieving high availability, scalability, and efficient content delivery through techniques like load balancing, CDN, and gray‑release strategies.
From the basics of three‑tier architecture to the challenges of scaling, this article explains why monolithic designs become problematic, how fine‑grained and coarse‑grained microservices address complexity, and offers practical refactoring steps for high‑concurrency systems.
This article explains core microservice concepts—including componentization, modularization, centralized vs. distributed systems, and the architectural principles behind microservices—while comparing them to SOA and highlighting practical distinctions that help developers design loosely‑coupled, reusable services.
The article shares a senior engineer’s perspective on evolving payment system architectures—from a simple monolithic WAR package, through a duplicated “chimney” style, to a fully modular micro‑service platform—highlighting why each generation fits different business stages and how domain‑driven design supports rapid market growth.
This article traces Spring's evolution, explains why Spring Boot was created to simplify configuration and deployment, outlines its core features, testing support, convention‑over‑configuration philosophy, and its relationship with Spring Cloud, providing a comprehensive guide for backend developers.
FinTech firms should replace monolithic systems with microservices because the modular style delivers greater agility, maintainability, scalability, availability, and code reuse—crucial for rapid market demands and regulatory change—while acknowledging migration costs, monitoring complexity, and the need for phased refactoring of legacy assets.
The article warns developers about the dangers of blindly following flashy technologies—such as over‑abstracted patterns, NoSQL hype, endless scalability promises, micro‑services mania, and agile buzzwords—by highlighting real‑world pitfalls and urging thoughtful, purpose‑driven engineering decisions.
This article explains the fundamentals of remote method invocation, compares traditional RMI with modern RPC frameworks, introduces Dubbo's architecture and roles, and provides a step‑by‑step guide to quickly develop, build, and run a complete Dubbo application using API‑centric configuration and multicast registration.
Cloud Foundry is an open‑source PaaS that abstracts cloud, framework, and service choices, offering features such as multi‑cloud deployment, standard frameworks, built‑in services, and a modular, message‑driven architecture composed of Router, Cloud Controller, DEA, Health Manager, Service Broker, and NATS, with flexible deployment options for both private and public clouds.
This article shares the design and implementation of a lightweight, robust, and low‑intrusion monitoring management system for microservice traffic, detailing data collection via client filters, Redis‑based structured storage, alerting, rate‑limiting, degradation, and authorization mechanisms, and discusses performance optimizations and future improvements.
This article describes Ant Financial's decade‑long service‑oriented architecture evolution, the challenges of multi‑language and legacy systems, the evaluation of Istio, Linkerd and Conduit, and the design and deployment of the internally built SOFA Mesh using a Golang sidecar and EdgeSidecar to achieve cloud‑native, high‑availability service mesh capabilities.
The article debunks three prevalent misconceptions—treating a development framework as a substitute for an architect, assuming high concurrency and big‑data challenges are inherently difficult, and believing microservice architecture is a universal solution—by emphasizing the importance of proper design, testing, and realistic evaluation of trade‑offs.
This article explains why banks should adopt blockchain systems, outlines three guiding principles, describes typical integration architectures, examines changes to reconciliation and transaction consistency, and offers practical solutions for identity verification, key management, and high‑availability deployment.
The article summarizes the design principles of reactive microservices, covering isolation, single responsibility, autonomy, private state, asynchronous messaging, service discovery, API management, and security, and explains how these concepts enable scalable, resilient cloud‑native systems.
The article explains how increasing business complexity and throughput demands drive system splitting—horizontal scaling, vertical and business sharding, and database partitioning—and describes the subsequent architectural evolution toward micro‑services, caching, indexing, and asynchronous processing to improve capacity, robustness, and performance.
In this interview, Ant Financial’s middleware leaders Yang Bing and Huang Ting discuss the evolution of the SOFA framework, the adoption of Service Mesh, open‑source strategies, cloud‑native transformation, and practical advice for engineers navigating large‑scale financial technology platforms.
This article explains how to construct a PaaS cloud platform using a microservice architecture, Spring Cloud Netflix components, Docker containers, and supporting services such as a gateway, Eureka registration, Hystrix fault tolerance, and a dynamic configuration center.
This article explains how to construct a PaaS cloud platform using microservice architecture and Docker containers, detailing the roles of Spring Cloud Netflix components such as Zuul, Eureka, Hystrix, and Config Server, and covering gateway routing, service discovery, deployment, fault tolerance, and dynamic configuration.
This article presents a practical, China‑centric microservices reference stack built on Spring Cloud, detailing eleven core components—including Zuul, Eureka, Apollo, Kafka, ELK, and Hystrix—while comparing them with alternatives and offering guidance for architects to avoid common pitfalls and accelerate production‑grade deployments.
This article explains microservices architecture, contrasting it with monolithic systems, outlines its core characteristics, communication patterns, advantages, disadvantages, design considerations, API importance, governance practices, fault‑tolerance strategies, container integration, and real‑world examples such as Netflix and Twitter.
This article explains how container technologies like Docker and Amazon ECS enable the transition from monolithic web applications to scalable microservices architectures by improving development agility, resource isolation, and deployment flexibility across cloud environments.
This article provides a comprehensive guide to planning, developing, testing, and monitoring microservices, recommending a range of open‑source tools for documentation, code review, logging, CI/CD, performance testing, and observability to help developers build reliable, scalable services.
The article outlines how to classify microservice-based systems into interface, web, and task categories, describes their architectural evolution, and provides a step‑by‑step methodology for identifying core (golden) functions and processes, distinguishing strong and weak dependencies, and implementing resilient disaster‑recovery strategies for large‑scale e‑commerce events.
This article applies the thermodynamic concept of entropy to software systems, explaining how entropy increase manifests as technical debt and how deliberate entropy reduction through architectural evolution, micro‑services, DevOps practices, and organizational changes can sustain system vitality and productivity.
The article explores how the concept of entropy from the second law of thermodynamics maps onto software systems and organizations, describing entropy increase and reduction, negative entropy, four governing rules, technical debt, progressive architecture patterns such as the strangler and refactoring approaches, and real‑world examples like Amazon’s evolution to microservices.
This article explains why growing business complexity and throughput demands force a system to be split and refactored, describing horizontal scaling, vertical and business splitting, database sharding, and the resulting architectural evolution toward micro‑services.
The article reviews how increasing business complexity and throughput demands drive the need to split applications and databases, adopt horizontal and vertical scaling, implement business and service-level partitioning, and evolve system architecture toward micro‑services, caching, and asynchronous processing.
This article demystifies service discovery, explains the roles of providers, consumers, and registries, explores using Redis as a lightweight registry with keep‑alive and versioning mechanisms, discusses extensions for non‑HTTP services, configuration reload, management UI, and presents a simple open‑source implementation.
Microservice architecture, introduced in 2012, breaks monolithic applications into independent services, offering benefits like scalability and flexibility while introducing challenges such as complexity, communication overhead, and testing, and the article explores its evolution, core characteristics, design patterns, implementation practices, and trade‑offs.
The article explains how distributed transactions work in microservice architectures, using inventory‑order examples and a World of Warcraft raid analogy to illustrate the XA two‑phase commit protocol, its normal and failure flows, limitations, and alternative approaches such as three‑phase commit, message‑queue and TCC transactions.
This article walks through the step‑by‑step implementation of a high‑throughput flash‑sale (seckill) service in Java, covering request flow, database schema, optimistic‑locking updates, Redis‑based rate limiting, CI scripts, and optional Kafka asynchronous order processing to achieve fast, reliable, and scalable sales handling.
This article explains how Conway's law guides functional team division in microservice architectures, describes decentralized governance, outlines various interaction and composition patterns, discusses fault‑tolerance mechanisms such as isolation, circuit breaking, rate limiting, and provides guidance on choosing appropriate service granularity.
This article explains how ServiceComb builds on Vert.x to support both reactive and synchronous communication modes, details the thread models for single and multiple connections, presents performance improvements through CAS queues and multi‑connection setups, and outlines flexible thread‑pool strategies for microservice providers and consumers.
An extensive overview of JD.com's microservice component platform explains its underlying architecture, communication technologies, service mesh (ContainerMesh), design tools based on DDD, service evaluation, migration challenges, and the platform's evolution toward a cloud‑native, self‑evolving ecosystem supporting distributed tracing, API gateways, and plugin‑based development.
The article explains the concept, functions, design goals, data models, log collection, and deployment considerations of distributed tracing systems, and compares several open‑source and proprietary solutions such as Dapper, Zipkin, Pinpoint, Alibaba Eagle Eye, and JD Hydra to guide the selection of an appropriate tracing platform.
This article explains how ServiceComb’s ServiceCenter component provides reliable microservice registration, discovery, and management through features like instance isolation, black‑white list control, asynchronous caching, heartbeat mechanisms, and self‑preservation, ensuring high availability in distributed cloud‑native environments.
The article systematically debunks six common container misconceptions—startup speed, density, image versioning, self‑healing, service discovery, and scaling—by comparing containers with virtual machines, then explains how containers fit into micro‑service and DevOps practices and outlines the scenarios where container adoption truly adds value.
This article explains Dubbo’s core RPC principles, architecture layers, design philosophy, open‑source growth, adoption by major enterprises, and upcoming plans for modularization, metadata, async support, and its progression through the Apache Incubator toward becoming a top‑level project.
