This article outlines ten essential microservices best practices—from domain‑driven design and independent databases to async communication, observability, and organizational alignment—providing a comprehensive guide for building scalable, maintainable service‑oriented systems.
This article explains the fundamentals of microservices architecture, detailing its definition, core principles such as small independent services and lightweight communication, the advantages and drawbacks, suitable organizational contexts, and the essential technical components like service discovery, gateways, configuration centers, monitoring, circuit breaking, and container orchestration.
This article details the background, goals, architecture, implementation, and future plans of the PASSPORT SDK developed to unify account systems across 58 Group apps, emphasizing a layered backend design, simple interfaces, black‑box service flows, and extensible features for mobile developers.
This article explains how to evolve a simple single‑node backend by adding a reverse proxy, introducing load balancers, scaling databases, adopting micro‑services, leveraging caches and CDNs, using message queues, and applying partitioning techniques to handle massive traffic while maintaining consistency and reliability.
This article provides a comprehensive overview of Toutiao's rapid growth and technical architecture, detailing its massive user base, data collection pipelines, user modeling, recommendation engines, storage solutions, message push mechanisms, micro‑service design, and virtualization PaaS platform.
To generate a user‑enriched order report in a microservice system, the article compares four approaches—direct DB access, REST data aggregation, batch pulling, and an event‑driven model—highlighting their trade‑offs in coupling, performance, scalability, and resilience, and recommends the event‑push solution.
This article walks through a typical image‑service architecture, detailing each step from the user's search query and DNS lookup through load balancing, caching, database access, asynchronous processing, search, cloud storage, CDN delivery, and final page rendering.
At CNBPS 2019, Tencent Cloud architect Kong Lingfei explained the evolution, architectures, and practical use cases of Serverless, detailing its three technical models, supporting tools, and real‑world deployments, illustrating how the shift to Function‑as‑a‑Service reduces operational overhead and accelerates product development.
This article explains how a CPU executes programs through the fetch‑decode‑execute cycle, describes instruction sets, registers, pipelines, superscalar and multithreaded designs, and details the cache hierarchy from registers to L3, providing a comprehensive overview of modern processor fundamentals.
This article explains how software architects can use UML‑based modeling to translate functional and non‑functional requirements into clear design documents, covering the essential steps, key concepts, and the seven major UML diagram types across requirement, conceptual, and detailed design phases.
Since 2017, Tencent Online Education has migrated its siloed, self‑developed services to a unified cloud‑native architecture—standardizing micro‑services, selecting open‑source middleware, and enhancing DevOps with Kubernetes, CI/CD, and data migration—thereby boosting development efficiency, scalability, cost savings, and fostering a collaborative engineering culture.
This article shares an Alibaba engineer’s comprehensive insights on wireless (mobile) architecture, covering stakeholder analysis, engineering structure, code coupling, component reuse, technology decisions, performance comparison of Flutter and Weex, tooling, stability, leadership, organization, modularization, and future expansion to help developers improve efficiency and product quality.
This article walks through the progressive transformation of a simple Java‑Web e‑commerce prototype—from a single‑machine setup to multi‑server clusters, load‑balancing, database read/write splitting, caching, sharding, service‑oriented architecture, and message middleware—illustrating practical solutions to scalability, reliability, and performance challenges.
This guide outlines the essential components of a startup’s backend architecture, covering language choices, middleware, databases, messaging, monitoring, CI/CD, and cloud services, and provides practical selection criteria and best‑practice recommendations to help teams design a robust, scalable, and maintainable system.
This article describes the redesign of a large‑scale Android instant‑messaging (IM) module, detailing the shortcomings of the original architecture, the new three‑layer framework, the split‑converter for parallel business‑line development, component‑based UI design, and the design‑pattern techniques used to achieve a maintainable, extensible solution.
System refactoring succeeds when the Dao—clear, measurable goals and incremental, risk‑controlled planning—guides the Shu of concrete techniques such as service‑oriented design, judicious caching, asynchronous processing, and sharding, while evaluating performance, availability, scalability, elasticity, security, and operability to balance trade‑offs.
This article explores the fundamentals of architecture and model thinking, defining their core elements, principles, and roles, and shows how architects and model thinkers use structured frameworks and abstract models to identify contradictions, devise optimal solutions, and guide system improvement across software, organizations, and broader contexts.
This article explains what a data middle platform is, why it matters, its core components—including storage, compute, IDE, workflow, API services, and data asset management—and details the layered architecture of ODS, DWD, DWT, DIM, and DWA, as well as dimensional modeling using Kimball’s methodology.
This tutorial walks through Android implementations of MVC, MVP (using Mosby), and MVVM (with DataBinding), providing concise explanations, annotated code snippets, and a unified demo that lets beginners quickly grasp the differences and start building each architectural pattern in just ten minutes.
Wedge is a Meituan‑Dianping advertising experiment configuration platform that provides extensible, flow‑based A/B testing with version control, real‑time monitoring, and a user‑friendly UI, enabling algorithm, engineering, and business teams to rapidly iterate, audit, and roll back complex vertical and horizontal experiments.
This article examines the architectural design of flash‑sale (seckill) systems, covering high performance through dynamic‑static separation, hotspot optimization, consistency handling for inventory deduction, and high‑availability techniques such as traffic shaping, queuing, and fallback plans.
The article explains how traditional Java web projects that rely on JSP tightly couple front‑end and back‑end, causing performance and scalability issues, and argues that modern large‑scale applications should adopt a decoupled architecture with static front‑end resources served by nginx and APIs delivered by backend services.
Over eleven years Alipay’s engineers transformed the daunting Double‑11 traffic surges from chaotic outages into a smooth, scalable system through relentless capacity planning, architectural revolutions, rigorous stress testing, and the adoption of the self‑developed OceanBase database, turning “impossible” goals into everyday reality.
After the Double‑Eleven sales surge, Xianyu transformed its transaction link from a fragmented, frontend‑decoupled design into a unified cloud‑native stack using Dart, Flutter, and FaaS, enabling cross‑platform UI, server‑side glue code, and reducing development effort from three engineers to one while boosting stability and scalability.
At the 2019 Hangzhou Yunqi Conference, Amap’s technical team detailed how they fused separate car‑machine and mobile clients into a unified engine, instituted architecture governance that cut compile and release times dramatically, and built a C++‑based dynamic rendering system that unifies Android and iOS, enabling rapid, cross‑platform feature delivery.
This article introduces the rapid growth of cross‑platform mobile solutions, explains why Flutter was chosen for a new project, details the engineering structure, resource and dependency management, mixed UI challenges, routing and communication mechanisms, and shares crash‑monitoring strategies and future outlooks.
Backend developer Xiao Ming designs an architecture for a photo‑ID app by identifying complexity in image storage and processing, prioritizing solutions such as local‑disk abstraction and Baidu AI services, and applying the principles of suitability, simplicity, and evolutionary design to produce a practical system.
This article presents ten GraphQL principles—grouped into integrity, agility, and operations—that guide the design, evolution, and secure large‑scale deployment of a unified data‑graph layer, emphasizing a single schema, collaborative implementation, schema registries, performance monitoring, and structured logging.
This article explains the core principles of CPU operation, covering the fetch‑decode‑execute cycle, instruction sets, registers, pipeline and superscalar designs, multithreading and multicore behavior, as well as cache hierarchy from registers through L1‑L3, illustrating how these mechanisms affect program execution.
The article shares Winter's presentation on building a high‑quality, efficient frontend team, covering demand models, toolchains, continuous integration, reusable architecture, business value, data‑driven thinking, and the Weex innovation case, while also providing recruitment information for the ZooTeam.
This article summarizes Alibaba Cloud Redis’s architecture, including single-node, high‑availability, cluster, read‑write separation, disaster‑recovery options, and hybrid storage, and details its kernel optimizations such as AOF/Binlog enhancements, multi‑threaded I/O, Memcache compatibility, and performance improvements.
KeyDB is a high‑performance, multithreaded fork of Redis that retains full Redis compatibility while delivering up to twice the query throughput and 60 % lower latency, and the article explains its thread model, connection management, fastlock mechanism, and active‑replica features in detail.
This comprehensive guide walks you through the fundamentals, design patterns, consistency models, core components, and engineering practices of modern distributed systems, helping you understand micro‑service architecture, network protocols, data management, fault tolerance, and performance optimization in cloud‑native environments.
The article examines the challenges of adopting microservice architecture, especially when refactoring monolithic applications, by discussing design rationale, risk assessment, mitigation plans, and how to manage conflicts between speed and quality to achieve a "good enough" solution.
This article introduces Kubernetes as an industrial‑grade container orchestration platform, explains its key functions, architecture, core API objects such as Pod, Deployment, Service, and Namespace, and walks through a practical Minikube demo covering scheduling, self‑healing, rolling updates, and horizontal scaling.
Flutter Web re‑implements the dart:ui library using HTML, CSS, and Canvas, allowing Dart‑written Flutter apps to run in browsers without plugins; it follows a layered rendering approach, supports image, text, shape, and gesture handling, but currently suffers from large bundle sizes, incomplete feature support, and performance challenges in technical preview.
The article reviews the September 21 cloud‑development salon, detailing how Mini‑Program cloud services simplify backend setup, introduce serverless cloud calls, real‑time database push, value‑added functions and network interconnect, and showcases practical use cases such as game data streaming, AI chatbots, SCRM construction and movie‑ticketing operations.
Beeshell 2.0, Meituan’s open‑source React Native component library, adds 38 functions across 33 components and 5 tools, employs a four‑layer architecture with a customizable hierarchy of theme variables to render props, ensures UI consistency via a shared design system, achieves over 80 % test coverage, and plans to grow to 100 + components while welcoming community contributions.
This article explains Elasticsearch X‑Pack's machine‑learning capabilities, covering supervised and unsupervised learning concepts, data preparation, task creation types, architecture components, data flow, result indices, and provides code examples for configuring and running ML jobs.
This article provides a detailed introduction to server fundamentals, covering architecture types, classification by instruction set and form factor, key hardware components such as CPUs, memory, BIOS/UEFI, cache, networking, storage, and management protocols, offering a comprehensive guide for IT professionals.
The article outlines the background, design principles, layered implementation details, and optimization considerations of a reusable, extensible basic framework architecture that separates business, functional, UI, and support layers to reduce coupling and accelerate app development.
This article walks through the transition of an online supermarket from a simple monolithic web application to a fully fledged microservice architecture, highlighting the challenges, design decisions, component choices, monitoring, tracing, testing, and operational practices needed for a robust, scalable system.
The article examines the evolving technical leadership needs of a fast‑growing beauty social‑ecommerce startup, contrasting the roles of senior developer, technical manager, technical director, architect and CTO, and explains why a founder may actually need a technical manager rather than a CTO at early stages.
This article outlines a systematic approach to designing and implementing a modular, multi‑layered application framework that separates business, functional, UI, and infrastructure concerns, enabling fast feature expansion, reduced coupling, and lower development and testing costs.
This article details Meituan's end‑to‑end development of a merchant‑side mobile video feature, covering background needs, architecture design, technology selection, implementation of playback, recording, composition, cutting, processing pipelines, encountered pitfalls, monitoring strategies, and future optimization directions.
This article reviews the evolution and key components of big data platforms at leading Chinese internet companies—Taobao, Didi, and Meituan—detailing their data sources, synchronization tools, storage layers, processing engines, and scheduling systems to provide practical guidance for building robust big data infrastructures.
The article presents the FoxPage Native platform developed by Trip.com to address homepage iteration challenges by using a JSON‑based DSL, Flexbox layout, and a modular architecture that enables high‑performance, dynamic, and multi‑device UI rendering with low development cost.
This article presents a comprehensive Java architecture roadmap for developers with two to five years of experience, covering design patterns, engineering tools, distributed systems, micro‑services, performance tuning, low‑level fundamentals, and practical project experience while advising against side‑project distractions.
This article explains the fundamentals, data model, storage options, synchronization strategies, metadata handling, and scaling considerations for building a high‑performance feed‑stream system used in social platforms such as micro‑blogs, friend circles, and short‑video feeds.
The article explains how built‑in quality integrates architectural, design, code, system, and release practices into every development increment to ensure fast, sustainable delivery, reduce defect costs, and support both software and hardware systems in agile and lean environments.
This article explains the differences between structured, semi‑structured and unstructured data, walks through the evolution stages of relational database architectures, evaluates their advantages and drawbacks, and then compares major NoSQL families—KV, search, column‑oriented and document stores—to help engineers decide the right storage engine for their workloads.
This article examines the rise of edge computing, explaining why it has become essential in the 5G era, analyzing server‑side and client‑side constraints, classifying edge product types, outlining its business and technical value, and offering principles and concerns for adopting edge architectures.
This article presents a comprehensive overview of Club Factory's recommendation system, covering its product recommendations, key challenges such as user and item cold‑start, the modular architecture, detailed recall and ranking processes, and practical considerations for deployment in e‑commerce.
The article explains how testers can improve software quality by actively reviewing API definitions, understanding system architecture, evaluating database designs, reading code, and mastering configuration files, turning testing from a final checkpoint into a proactive, integral part of the development lifecycle.
This article chronicles a Java backend data‑migration project where the author transformed a two‑month, 2000‑million‑record process into a four‑hour job by iteratively redesigning the architecture from a monolithic procedural approach to a fully decoupled, multithreaded, queue‑driven system, highlighting key performance bottlenecks and solutions.
This article presents Xianyu's intelligent publishing solution that leverages real‑time mobile AI to automatically associate user‑uploaded items with existing catalog entries, balancing low user cost, high accuracy, and system performance through a multi‑layer architecture and flexible pipeline design.
This article examines common misuse of base Controller and Service classes in Java Spring projects, explains why they violate the Liskov Substitution Principle, and provides practical steps to split, refactor, and properly structure code across the three‑tier architecture.
This article chronicles the architectural evolution of the BeChat kindergarten parent platform, detailing three major redesigns—from a simple LNMP monolith to a Java‑based distributed system and finally a Dubbo‑driven microservice architecture—while outlining the technical motivations, challenges, and future plans such as Docker containerization, API‑gateway integration, and multi‑IDC deployment.
This article explains how Meituan‑Dianping built the CAT platform to provide both user‑side and server‑side real‑time monitoring at trillion‑event scale, detailing its metrics, architecture evolution, storage strategies, and open‑source contributions.
The article offers a comprehensive overview of backend development, explaining core system design principles, architectural patterns, network communication techniques, fault handling strategies, monitoring and alerting practices, service governance mechanisms, testing methodologies, and deployment workflows, from high cohesion and scaling to gray‑scale releases and rollbacks.
This article provides a comprehensive, illustrated explanation of Apache HBase's architecture, covering its master‑slave components, region management, Zookeeper coordination, data flow for reads and writes, storage structures, compaction processes, fault recovery, and the system's strengths and limitations within the Hadoop ecosystem.
This article traces the historical evolution of frontend development—from early monolithic web architectures through the rise of distributed systems and front‑end/back‑end separation, to modern serverless and Backend‑for‑Frontend (BFF) approaches—highlighting the shifting roles, challenges, and emerging solutions in the industry.
This article presents thirty concise architecture principles covering simplicity, YAGNI, iterative development, testing, ROI, user focus, modular design, configuration, concurrency, distributed systems, and user experience, offering practical guidance for backend engineers to build scalable, maintainable software.
This article discusses why microservices have become popular, outlines their advantages such as continuous delivery, easier maintenance, independent scaling, fault tolerance, and technology flexibility, and also examines the challenges like service decomposition, distributed system complexities, and multi‑team coordination, helping readers decide when to adopt them.
This article introduces Node.js by covering its origins, core architecture, key features such as event‑driven non‑blocking I/O, and the scenarios where it excels, helping readers decide when and why to choose Node.js for backend development.
This article explains how microservices differ from traditional monolithic delivery, outlines the five key architectural constraints—scalability, elasticity, composability, minimality, and completeness—and provides practical guidance for designing robust, loosely‑coupled services.
This article explains MX Player’s recommendation engine architecture, detailing the division between functional and algorithmic components, API communication via Thrift, and the configurable core processing pipeline that handles recall, filtering, scoring, ranking, rule‑based adjustments, packaging, and caching.
The talk explained how the surge of IoT, AI and 5G drives edge computing—originating from shifts in IT architecture toward micro‑services—and described its layered hardware‑software ecosystem, Docker‑based core and cloud orchestration, dual management modes, key components, use cases such as smart transport and factories, future trends, and a hands‑on demo of deploying an edge node and rule‑engine.
This article examines the evolution of Java microservices at Huajiao, compares existing PHP and Java solutions, justifies the adoption of Spring Boot 2 with MyBatis and Undertow, outlines incremental improvements such as CI/CD migration and service mesh adoption, and presents a roadmap for future microservice components.
This article chronicles the development of the x86 and ARM ecosystems, detailing early competitors, strategic alliances, technological shifts, market battles, and future trends that have shaped the semiconductor industry and the broader computing landscape.
This article provides a comprehensive overview of HBase, covering its distributed column‑oriented architecture, data model components, storage mechanisms, read/write processes, WAL lifecycle, MemStore flushing, region splitting and merging, and failure recovery within the Hadoop ecosystem.
The article traces Taobao's backend architecture evolution—from a single‑machine setup through caching, load balancing, database sharding, microservices, containerization, and cloud deployment—illustrating the technologies and design principles needed to scale from hundreds to tens of millions of concurrent users.
Distributed architecture, built on networked software systems, offers cohesive, transparent services through concepts like cohesion, transparency, and various applications such as distributed file systems, caches, databases, and web services, while evolving through stages like caching, clustering, load balancing, and addressing challenges like service management and scalability.
This article chronicles the evolution of MaFengWo's instant‑messaging platform, detailing the transition from a simple PHP implementation to OpenResty optimizations, the introduction of multi‑mode routing in IM 2.0, and a complete service‑oriented redesign in Go for IM 3.0, while addressing scalability, multi‑device synchronization, and message reliability.
This article traces Taobao’s backend architecture evolution from a single‑server setup to a cloud‑native, micro‑service ecosystem, detailing each scaling stage—separating Tomcat and database, adding caches, load balancers, read/write splitting, sharding, NoSQL, ESB, containers, and finally public‑cloud deployment—while highlighting the associated technologies and design principles.
This article explains TDengine’s architecture, including its management, data, and client modules, virtual node design, write process, and detailed storage file structures, highlighting how its innovative design optimizes resource usage and performance for IoT and other big‑data applications.
This article walks through Taobao's architectural evolution—from a single‑server setup to distributed clusters, caching, load balancing, microservices, containerization, and finally cloud platforms—illustrating the technologies and design principles needed to handle hundred‑to‑hundred‑million concurrent requests.
This article introduces the fundamentals of microservices and reactive systems, explains how reactive programming integrates with microservice architectures, compares traditional and reactive approaches, outlines core components, design principles, and technology choices such as Spring Cloud, and provides guidance for building scalable, resilient reactive microservices.
At a Cloud+ Community salon on June 29, nearly 300 developers heard Tencent Cloud detail mobile co‑hosting live streaming, P2P‑accelerated CDN, globally distributed overseas streaming architecture, RTC‑to‑PSTN integration, and AI‑driven video services such as recognition, moderation, compression, editing, and highlight extraction.
This article explains the essential considerations for creating overall and application‑level architecture diagrams, covering layered structures, SOA‑based service layers, distinctions between business and technical views, and practical tips for visualizing enterprise, IoT, and single‑system architectures.
When creating software or solution architecture diagrams, it is essential to consider layered structures, platform and service distinctions, SOA principles, and the separation of application and technical views to effectively communicate enterprise‑wide or single‑system designs.
This article details how a team of web developers chose Electron to create a cross‑platform PC client for the teaching tool "Classroom Optimization Master", describing the technology stack, successive architectural evolutions, performance improvements, and lessons learned about modular design and hot updates.
The article describes Autohome's evolution from a Zabbix‑based monitoring setup to a custom, distributed monitoring platform, detailing its architectural components, design goals, implementation choices, product features, and future roadmap for fault localization and dynamic alerting.
This article recounts the evolution of the Class Optimization Master Android project—from a dual‑end, no‑design prototype to an MVP‑based implementation and finally a modularized architecture—highlighting pain points, solutions, and practical steps for improving code boundaries, build times, and reusable modules.
This article examines Xianyu's adoption of Flutter, detailing its benefits for small and Android‑focused teams, the technical hurdles of integrating Flutter into existing apps, memory‑optimized engine sharing, video rendering improvements, the evolution of the Fish Redux framework, and the automation pipeline that drives efficient, data‑backed development.
This article describes the motivation, architecture, key components, rule engine, alert actions, and practical lessons learned while building a unified monitoring and alarm system for MaFengWo's large‑scale transportation platform, highlighting data collection, Elasticsearch storage, scheduling, and future enhancements.
This article traces the evolution of internet architecture from simple single‑instance Java projects through Nginx load balancing, HA clusters, CDN, database read/write separation, NoSQL, distributed search, sharding, distributed file systems, service decomposition, and finally microservice architectures, explaining the motivations, techniques and trade‑offs of each stage.
This article provides a comprehensive, illustrated guide to the entire manufacturing workflow of an Intel Core i7 CPU—from raw silicon extraction and purification, through photolithography, doping, and multilayer metal deposition, to testing, packaging, and future architectural outlooks including x86 limitations and the rise of RISC‑V and the RIOS lab.
The paper presents a high‑performance real‑time data processing pipeline that collects, transports, preprocesses, and computes service logs and metrics using Alibaba Logtail, LogHub, and an enhanced Flink (Blink) engine, persisting root‑cause graphs in Lindorm, achieving sub‑3‑second latency for tens of millions of events per second and cutting diagnosis time to about five seconds.
This article examines why monolithic, tangled codebases—dubbed the Big Ball of Mud—fail due to performance, complexity, and organizational mismatches, and presents a series of concrete architectural remedies such as domain modeling, service decomposition, ESB avoidance, asynchronous messaging, and event sourcing to achieve stable, maintainable systems.
The article explains how organizations can achieve rapid growth by openly acknowledging failures, creating lightweight post‑mortem processes, and continuously learning from mistakes, illustrated through Intuit’s SaaS transition, PayPal’s rollback challenges, and practical rules for QA and architecture.
This article uses Taobao as a case study to trace the evolution of a backend system from a single‑machine setup to a multi‑layer, highly available, horizontally scalable architecture that can handle tens of millions of concurrent users, summarizing key technologies and design principles at each stage.
This resource compiles a complete series of articles on distributed system theory covering consistency, consensus, high availability, scalability, performance, testing, and operations, offering both quick overviews for newcomers and in‑depth readings for practitioners seeking to master modern distributed architectures.
This article explains SonarQube’s architecture, detailing its server, database, plugin library, and scanner components, and describes the typical development workflow from IDE integration and code commit through CI‑triggered analysis, result submission, and code review, including deployment considerations for machines and network placement.
In a May 25 Tencent salon, senior engineer Han Xin traced cloud‑computing’s shift from monolithic J2EE to container‑based microservices, explained service‑mesh and middle‑platform concepts, and showcased Tencent Service Framework’s governance, DevOps and reusable capabilities, emphasizing that simple, fast architectures must directly serve business value.
This article uses Taobao as a case study to illustrate how a web service evolves from a single‑machine setup to a cloud‑native, micro‑service architecture capable of handling tens of millions of concurrent requests, detailing each technical milestone and the principles behind the design choices.
This article uses Taobao as a case study to trace the step‑by‑step evolution of server‑side architecture from a single‑machine deployment to distributed clusters, caching, load‑balancing, database sharding, micro‑services, containerization and finally cloud platforms, summarizing the key technologies and design principles at each stage.
The article explores TiDB’s evolution philosophy, detailing its core beliefs, early user stories, and the three‑step "Make it work, make it right, make it fast" approach, while covering technical choices such as cloud‑first design, hardware‑agnosticism, formal verification, massive testing, performance tuning, and cost‑effective scaling.
In a DTCC 2019 keynote, Zhao Qun, director of big‑data platform at Percent Point, outlines the challenges of trillion‑scale real‑time analytics and presents a transparent, fine‑grained architecture built on Kafka, Spark Streaming, ClickHouse, HBase, Ceph and Elasticsearch, detailing design principles, component sizing, multi‑center deployment, performance testing and operational safeguards.
Xianyu’s team presents FlutterBoost, a reusable, non‑intrusive hybrid framework that lets large native Android/iOS apps progressively adopt Flutter by sharing a single engine, mapping native containers to Flutter widgets, supporting complex navigation patterns, and optimizing performance for billions of users.
