This article introduces the core concepts of building a cloud‑native microservice platform with Spring Cloud and Docker, covering configuration management, service discovery, circuit breakers, API gateways, mixed persistence, and provides a step‑by‑step guide to clone, build, and run the example project.
The article explains microservice architecture as a lightweight, service‑oriented approach where each service performs a single, well‑defined function, runs in its own process with an independent database, can be deployed separately on various platforms, and communicates via HTTP or other lightweight protocols, highlighting its key characteristics and benefits.
This article provides a comprehensive update on how microservices, containers, and cloud‑native architectures are reshaping middleware, covering key concepts, frameworks, CI/CD pipelines, service discovery, dynamic configuration, scalability, resilience patterns, and integration platforms for modern enterprise IT.
This article examines the contentious debate between microservices and SOA, explains their differing definitions, explores how API management bridges the two, and outlines the advantages, challenges, and key considerations for adopting microservices in modern, agile, and scalable enterprise architectures.
This article provides a comprehensive tutorial on using Alibaba's Dubbo framework to configure cluster fault‑tolerance modes, load‑balancing strategies, provider and consumer implementations, deployment steps, and management/monitoring tools, including code examples and custom extension points.
This article examines the analysis and optimization of a high‑traffic e‑commerce website, covering problems such as server waste and tight coupling, and presenting solutions including business splitting, application clustering, multi‑level caching, distributed sessions, and deployment diagrams to improve scalability and reliability.
This article explains the fundamentals of RESTful architecture—including resources, uniform interfaces, URIs, statelessness—and compares it with ROA, SOA, and RPC, while also covering authentication methods such as Basic, Token, and OAuth, offering practical guidance for building robust microservice APIs.
This article describes how a rapidly growing company refactored an outdated .NET contract management system into a set of independent microservices using the Stencil Ruby framework, detailing the motivations, microservice fundamentals, benefits, development workflow, deployment automation, and the resulting flexible architecture.
This article explores microservice architecture fundamentals, compares synchronous and asynchronous communication, details RabbitMQ’s AMQP model, optimization techniques, high‑availability configurations, flow‑control mechanisms, and shares practical case studies from NetEase’s Hive platform, offering actionable insights for reliable, scalable message‑queue deployments.
Uber’s adoption of microservices showcases both the flexibility of using multiple languages and independent release cycles, while also exposing challenges such as duplicated effort across teams, type‑unsafe JSON interfaces, and the need for rigorous failure testing, offering valuable lessons for large‑scale system design.
Wix, the world’s largest DIY website‑building platform, transformed its monolithic Java stack into a 100‑plus microservice architecture built on Scala, Jetty, and Spring, supporting 60 million sites across 190 countries with robust media services, SDKs, and modern front‑end frameworks.
500px handles massive image uploads and billions of daily views by leveraging a Go‑based microservice architecture on AWS, using Nginx, HAProxy, RabbitMQ, and VIPS to achieve up to 1000 requests per second with sub‑180 ms response times.
This article recounts how a rapidly growing online platform transformed a tightly coupled, fragile architecture into a scalable, high‑availability system by applying dynamic/static separation, read‑write splitting, caching, load‑balancing, intelligent monitoring, and finally migrating to a micro‑service architecture.
This article details Uber's transition to a modular microservice architecture, describing the RFC process for new services, the design and implementation of the Tincup currency service, and the technologies—such as MVCS, UDR, Tornado, TChannel, and Thrift—used to ensure scalability, reliability, and efficient production deployment.
This article traces cloud computing’s history from early grid and parallel computing concepts, through the rise of service-oriented models and virtualization, to today’s cloud‑native architectures, highlighting its transformation into a fine‑grained, on‑demand public resource.
This article traces the historical and technical evolution of cloud computing—from its early grid‑computing roots and the shift to service models, through the progression of isolation layers (physical machines, virtual machines, PaaS, containers), to the emergence of cloud‑native microservice architectures and their resource‑centric characteristics.
The article examines the challenges of maintaining data consistency across distributed services in e‑commerce, explains strong, weak and eventual consistency models, and presents six practical solutions—including business integration, the eBay BASE pattern, Qunar, Mogujie, Alipay DTS, and Nongxin—highlighting how local transactions, idempotent messaging, and eventual consistency can replace heavyweight distributed‑transaction frameworks.
The article chronicles Autohome's mobile backend transformation from a monolithic ALL‑IN‑ONE design to a modular, high‑availability microservice architecture, detailing the challenges of traffic surge, resource coupling, and rapid releases, and describing the adopted solutions such as service decomposition, stateless design, Java migration, RPC framework, asynchronous components, and comprehensive monitoring and tracing.
The article outlines how a startup with limited physical servers can build a cost‑effective, highly available IAAS using OpenStack, extend it with a CAAS layer based on Kubernetes, and then design a microservice architecture with command‑event separation, network and storage virtualization, and governance mechanisms to support rapid business growth.
This article explains how Netflix uses the open‑source EVCache system, built on Memcached and Kafka, to provide highly reliable, low‑latency caching for its micro‑services architecture across multiple AWS regions, handling billions of objects and millions of requests per second.
This article examines how a large‑scale e‑commerce transaction platform achieved high availability through iterative architectural evolution—from early .NET monoliths to vertical and horizontal micro‑service splits—highlighting practical strategies for fault detection, rapid recovery, scaling, and operational best‑practices.
The article explains Netflix’s EVCache—a cloud‑native, memcached‑based distributed cache that provides low‑latency, high‑reliability data access across multiple regions using asynchronous Kafka‑driven replication, detailing its architecture, performance optimizations, and remaining challenges.
This article explains the fundamentals of microservices architecture, contrasting it with monolithic and SOA approaches, and details design principles, messaging patterns, integration styles, data decentralization, governance, service discovery, deployment with Docker and Kubernetes, security, transaction handling, and fault‑tolerance techniques.
The article explores the multiple demands on internet systems, explains why business service granularity is the biggest obstacle to microservice adoption, and shares practical insights on designing a cloud‑native platform with Docker, Kubernetes, unified monitoring, API governance, and multi‑tenant resource isolation.
This article, based on the Efficient Operations Community Talk, outlines the evolution of e‑commerce systems, the challenges faced during rapid growth, and how LeTV’s e‑commerce cloud leverages micro‑service architecture, container technology, and hybrid cloud solutions to address scalability, security, and operational efficiency.
This article details how Kuaidi Dache scaled from 2013 to 2015 by addressing LBS performance limits, redesigning long‑connection services, refactoring monolithic code into layered services with Dubbo and RocketMQ, building a secure open platform, implementing Storm‑based real‑time monitoring, and migrating data storage to sharded MySQL, Canal‑driven sync, and HBase for massive scalability.
The article examines the challenges of distributed transactions in large‑scale microservice architectures and compares three main approaches—traditional two‑phase commit, stateless queue‑based eventual consistency with event sourcing and CQRS, and transaction compensation techniques such as TCC—highlighting their trade‑offs and real‑world examples like Flipkart.
This article examines why many web projects pair a fast‑changing PHP front‑end with a stable, high‑performance Java back‑end, outlining each language’s strengths, recent improvements, integration methods, and architectural patterns such as view‑first and RPC/RESTful communication.
This article examines Uber's rapidly growing real‑time dispatch platform, detailing its geo‑spatial indexing, microservice architecture, fault‑tolerant design, and scaling techniques that enable millions of writes per second and high availability across thousands of nodes.
The article examines the paradox of the Chinese securities industry—high demand for cutting‑edge trading, quantitative and high‑frequency systems versus outdated IT—while detailing the team’s FinTech startup approach, their Node.js/Docker/MongoDB stack, a cloud‑native trading platform, microservice architecture, big‑data pipelines, performance tuning, and DevOps practices.
LinkedIn grew from a single monolithic Leo server handling all web requests to a complex ecosystem of over 750 independent services, employing graph databases, read replicas, caching layers, Kafka pipelines, Rest.li APIs, and multi‑data‑center deployments to support billions of daily queries.
This article explains the concept of microservices, contrasts it with monolithic architectures, outlines nine characteristic principles such as componentization, business‑capability‑oriented teams, product thinking, smart endpoints, decentralized governance, polyglot persistence, infrastructure automation, fault‑tolerance, and evolutionary design, and discusses the benefits, challenges, and practical considerations of adopting this style.
This article shares Cookpad’s practical experience with microservices, covering service granularity, RESTful integration, parallel processing, fault tolerance, testing strategies, logging, Docker‑based deployment pipelines, and company‑wide support mechanisms that together improve development speed and reliability.
The article reviews the challenges Docker introduces to traditional virtualization networks, explains the concepts of SDN, compares three open‑source container SDN solutions (Flannel, Calico, Weave), and details Qiniu's practical implementation of overlay networking, OpenFlow control, service discovery, load balancing, and security groups for microservice architectures.
The article explains how breaking a monolithic website into independent microservices improves stability, resource utilization, and deployment speed, but introduces client‑side complexity that can be solved by introducing a service gateway to aggregate APIs, enhance security, and simplify maintenance.
This article explains the layered architecture of Alibaba's open‑source Dubbo framework, detailing its service, config, proxy, registry, cluster, monitor, protocol, exchange, transport, and serialization layers, as well as service definition, registration, monitoring, communication protocols, and package organization for building distributed backend services.
The article explains three primary load‑balancing and service‑discovery patterns for microservice architectures—centralized external load balancers, client‑side soft load balancing, and independent host‑level LB processes—detailing their mechanisms, advantages, drawbacks, and real‑world examples such as F5/HAProxy, Netflix Eureka/Ribbon, and Airbnb SmartStack.
The article explains three primary load‑balancing and service‑discovery patterns for microservice architectures—centralized external load balancers, client‑side soft load balancing, and independent LB processes—detailing their mechanisms, advantages, drawbacks, and real‑world examples such as Netflix Eureka, Dubbo, and Airbnb SmartStack.
The article recounts ChuYe's evolution from a monolithic setup to a clustered micro‑service architecture, detailing the challenges of debugging, deployment, and monitoring, and describing the solutions implemented—including service clustering, automated deployment platforms, Docker usage, and comprehensive logging and audit systems—to improve agility and operational efficiency.
The article examines how microservices and container technologies are reshaping software development, operations, and organizational structures, emphasizing faster delivery, monitoring, contractual APIs, and the emergence of cloud‑native platforms such as Docker, IBM Bluemix Garage, Joyent Triton, and VMware solutions.
The article chronicles Xiaomi Web's architectural journey from a simple three‑engineer monolith in 2011 through systematic service decomposition, asynchronous messaging, database sharding with Cobar, cloud‑native scaling, advanced caching, virtual inventory allocation, and sophisticated monitoring, illustrating practical lessons for building high‑performance e‑commerce platforms.
This article chronicles LinkedIn's evolution from a monolithic Leo application to a massive micro‑service ecosystem, detailing the introduction of member graphs, read‑only replicas, caching layers, Kafka pipelines, Rest.li APIs, super‑blocks, and multi‑data‑center strategies that enable handling billions of requests daily.
This article explains how Docker containers improve security through isolation, Linux namespaces, cgroups, capabilities, and image management, while also covering integration with virtual machines, bare‑metal deployment, lifecycle management, and open‑source security practices for modern microservice architectures.
This article shares practical insights on achieving high availability by understanding goals, decomposing requirements, designing resilient architectures, ensuring operability, testing rigorously, and reducing release risk, illustrated through the multi‑stage evolution of a transaction system.
The article outlines the three core traits of internet architecture—agility, scalability, and openness—illustrates them with Alibaba’s supply‑chain and product examples, and explains how cloud‑based, distributed systems enable enterprises to become operators of their own core capabilities.
The article chronicles Yirendai’s four‑stage backend evolution—detailing the bottlenecks, architectural redesigns, logging improvements, and service‑splitting strategies that transformed a single‑server system into a scalable, multi‑service platform.
This article explains what microservices are, compares them with monolithic architecture, outlines their key characteristics, and provides practical guidance on client access, inter‑service communication, service discovery, fault tolerance, and deployment considerations.
This article explains how microservices emerged to address low development efficiency, technology incompatibility, and resource waste, and describes their benefits such as faster deployment, technology flexibility, optimal resource use, and improved stability, while also noting performance challenges.
This article chronicles JD.com's POP platform evolution from a simple monolithic system in 2010 to a micro‑service‑based, highly scalable architecture by V3.0, highlighting the technical challenges, solutions, and the introduction of service‑oriented APIs, diversified data stores, and unified operational tools.
Facing explosive growth in 2013‑2014, Kuaidi Dache re‑engineered its ride‑hailing platform by partitioning MongoDB, replacing single‑queue NICs with multi‑queue, rewriting its long‑connection service with AIO, adopting Dubbo and RocketMQ for micro‑services, and building a Storm‑HBase real‑time monitoring and data synchronization pipeline.
This article presents a detailed walkthrough of Meizu’s real‑time push platform, covering its four‑layer architecture, high‑concurrency design, micro‑service RPC framework, power‑saving strategies, duplicate‑message handling, DNS reliability, load‑balancing tactics, monitoring setup, and gray‑release deployment.
This article chronicles the architectural journey of JD’s Dongdong instant‑messaging platform, detailing its early simple polling design, subsequent performance and scalability challenges, and the progressive shifts toward service‑oriented, micro‑service, and cloud‑native architectures that support massive user growth.
In this interview, Meizu system architect Yu Xiaobo shares practical insights on high‑concurrency distributed systems, language choices, long‑connection heartbeat handling, and the evolution of their real‑time push platform, offering concrete advice for backend engineers facing massive user growth.
The talk explains how Docker’s container‑based development model transforms traditional development‑operations workflows, addressing issues such as opaque release pipelines, poor deployability, and monolithic architectures, and shows how Docker combined with CI/CD, microservices, and Kubernetes can streamline testing, accelerate delivery, and reduce operational complexity in enterprise environments.
This article examines Uber's rapid 38‑fold growth and the engineering choices behind its real‑time market platform, detailing the scheduling system, geographic indexing, microservices, Ringpop, TChannel, and strategies for scalability, availability, and fault tolerance.
This article explains how IBM Research leverages Spark to capture and analyze network traffic of microservice‑based applications in an OpenStack cloud, providing real‑time transaction tracing and batch latency statistics to reveal service dependencies and performance bottlenecks.
This article explains why microservices outperform monolithic architectures by detailing their design, deployment, benefits, and challenges, helping developers decide if the approach suits complex, evolving applications; it also compares traditional single‑code‑base models, discusses scaling strategies, and outlines practical considerations for implementation.
The article explains microservice architecture as a set of independently deployable services each focused on a single function, illustrating their roles, communication methods, deployment considerations, and key characteristics such as single responsibility, own data storage, and replaceability.
This article details Uber's rapid growth and the engineering choices behind its real‑time dispatch platform, covering geospatial indexing, microservice architecture, scaling techniques like Ringpop and TChannel, and strategies for availability and fault tolerance.
Tracing the evolution from early SOA concepts to today’s microservice architecture, this article examines their historical roots, contrasts their design philosophies, and outlines the operational, scalability, and security challenges developers face when adopting microservices in modern cloud-native environments.
This article explores why Laravel has become the most successful PHP framework, highlighting its modular architecture, extensive package ecosystem, micro‑service support through Lumen, elegant routing, middleware security, caching, authentication, task automation, encryption, ORM, testing, and queue handling.
This article presents a detailed overview of Snowball's backend architecture, technology stack, service decomposition, and the series of performance and scalability optimizations—including quote server, IM service, database caching, monitoring, and deployment strategies—implemented to support rapid growth and market volatility.
Industry veterans outline ten pivotal concepts—from Industry 4.0 and “Internet+” to microservices, distributed systems, big data, multi-screen integration, Docker, OpenStack, and platform‑microapp strategies—highlighting how enterprise software architecture is evolving toward more agile, loosely‑coupled, cloud‑native ecosystems.
The article distills ten pivotal keywords—Industrial 4.0, Internet+, BFV, microservices, distributed systems, big data, multi‑screen fusion, Docker, OpenStack, and large‑platform micro‑apps—explaining how each shapes the evolution of enterprise software architecture and what challenges and opportunities they bring.
Since the 1970s databases have become essential middleware, and modern large‑scale parallel databases, designed for extreme parallelism on clustered hardware, face trade‑offs in performance, scalability, and fault tolerance, prompting a shift toward cloud‑native, micro‑service architectures and new hardware such as SSDs and memory‑centric designs.
This article explains how Docker bridges the gap between microservices and operations by standardizing packaging, simplifying multi‑language integration, enabling automated testing and continuous delivery, and reducing the complexity of system evolution and deployment.
At QCon London, GDS architect Michael Brunton‑Spall explained how DevOps principles underpin successful microservice operations, covering service identification, initial creation, ownership, essential tooling, monitoring depth, failure handling, and practical deployment practices for scaling from a single service to a full ecosystem.
This article describes how a legacy .NET contract management system was transformed into a set of independent microservices using a strategic decoupling approach, explains microservice fundamentals and advantages, and introduces the Ruby‑based Stencil framework with code generation, CI templates, and one‑click AWS deployment to accelerate development and operations.
The article surveys this year's hottest technology trends—including the rise of public cloud, containerization, microservices, multi‑cloud management, endpoint security, machine learning, and the resurgence of DevOps—explaining why they are reshaping enterprise IT and why open source is the common driver behind them.
The article examines the evolution from traditional SOA and ESB to modern microservices, outlining key characteristics such as componentization via services, business‑aligned team structures, treating services as products, lightweight communication, decentralization, automation, failure‑tolerance, and evolutionary design, while discussing practical adoption challenges.
The article analyzes how long‑running software projects inevitably suffer architectural decay due to growing codebases, team size, and build complexity, and proposes practical strategies such as modularization, phased and distributed builds, component isolation, and disciplined technology adoption to keep systems sustainable.
