This article reviews the essential concepts of message‑queue middleware, covering why they are needed, their drawbacks, how to choose among popular solutions, and practical techniques for ensuring high availability, avoiding duplicate consumption, guaranteeing reliable delivery, and preserving message order.
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 introduces core architecture analysis methods—including system engineering, system decomposition, process‑oriented, and object‑oriented approaches—and compares monolithic (ALL IN ONE) and distributed system structures, providing practical examples and visual diagrams.
The article outlines the four major stages of enterprise IT architecture—single‑machine, dual‑machine hot‑standby, multi‑node active‑active, and distributed architectures—explaining their motivations, advantages, limitations, and how businesses should choose the appropriate model based on performance, availability, and scalability requirements.
This article outlines guiding principles, high‑availability strategies, and high‑concurrency techniques—covering stateless design, resource isolation, quota management, monitoring, degradation, rollback, and scaling—to help engineers build resilient, scalable systems while balancing cost and performance.
This article examines the evolution of a web crawler architecture across three versions, highlighting the importance of completeness, standardization with UML, clear goals, accuracy, and maintainability to build a scalable and cost‑effective backend system.
This article surveys the evolution of schedulers—from early batch systems and OS process schedulers to modern centralized, two‑level, and shared‑state designs—explaining their core concepts, trade‑offs, and real‑world examples such as YARN, Mesos, Spark, Borg, and Kubernetes.
The article explains how to describe system architecture from various perspectives, introduces logical and physical views, presents the 5‑view method, and outlines six practical steps—from requirement analysis to architecture validation—guiding architects to create adaptable, scalable, and maintainable designs.
This article outlines essential distributed system concepts—including system decomposition, concurrency, caching strategies, online vs. offline processing, push/pull communication, load limiting, service degradation, CAP theorem, and eventual consistency—to help engineers design scalable, reliable architectures for high‑traffic applications.
The article argues that software architecture is fundamentally the practice of uncovering a problem’s essence—its context, goal, and obstacle—classifying it as abnormal or improvement, and then converting the open‑ended gap between current state and desired outcome into a concrete, implementable solution.
This article explores the challenges and essential practices of software architecture, explaining its scope, how to create actionable designs, the architect's role, and ways to cultivate architectural thinking through experience and continuous improvement.
Compiled from extensive interview experiences, this guide presents a comprehensive set of Java interview questions spanning core language concepts, data structures, concurrency, Spring IoC, networking fundamentals, operating system principles, distributed system challenges, Redis mechanisms, system design scenarios, big‑data problem solving, and classic logical puzzles.
This article explains how the complexity of software requirements can be managed using the RUP 4+1 view method, illustrating the approach with a supermarket system and a device debugging system to ensure every functional and non‑functional need is systematically satisfied.
The article recounts JD.com architect Li Biao’s transition from traditional software to internet engineering, detailing how he resolved a critical Oracle database outage by building a task‑driven engine, applied component‑based design in the 7FRESH project, and shares his insights on system architecture, team building, and continuous learning.
The article argues that software architecture is a real design discipline composed of multiple topics and logical layers, illustrating its necessity through examples like telephone exchanges and network driver development, and warns against ignoring architectural planning in complex, evolving systems.
The article explores the essence of software architecture as a disciplined process of reducing system entropy through strategic decomposition and recomposition, outlines the roles of business, application, and technical architecture, describes the architect’s capability model, and presents four progressive levels of architectural mastery.
This article examines Baidu’s Cluster Control System (CCS), detailing its two‑level data model, four‑tier scheduling architecture, and three‑layer execution agents, and explains how control and execution information, redundancy, and fault‑tolerant designs enable reliable large‑scale command execution across thousands of servers.
This article introduces the concept of architecture patterns, outlines ten common software architecture styles—including layered, client‑server, master‑slave, pipe‑filter, proxy, peer‑to‑peer, event‑bus, MVC, blackboard, and interpreter—detailing their structures, typical use cases, advantages, and disadvantages.
This article examines the challenges of rule‑driven development at Meituan, compares hard‑coded, Drools‑based, and custom rule‑engine solutions, and presents the design of the Maze framework that separates decision logic, supports hot‑deployment, and improves maintainability and performance.
An in‑depth recount of eight backend interview experiences across companies like Afanti, Guokr, Veeva, Zhihu, and ByteDance, detailing each round’s questions, technical challenges such as browser request flow, database design, and code snippets, while offering practical advice for aspiring Python developers.
This article presents the challenges of virtual product development and describes three engineering solutions—a Footprint tracking system, a Mock Server platform, and a pre‑release gray‑release strategy—detailing their backgrounds, architectures, implementations, and operational benefits for improving debugging, testing, and deployment efficiency.
Explore ten common software architectural patterns—including layered, client‑server, master‑slave, pipe‑filter, proxy, peer‑to‑peer, event‑bus, MVC, blackboard, and interpreter—detailing their structures, typical use cases, advantages, and drawbacks, to help you choose the right architecture for enterprise‑scale systems.
This article explores the seven core competencies—technical expertise, abstraction, design foresight, systematic thinking, problem‑solving depth, cross‑domain knowledge, and communication—that distinguish a successful software architect and guide how to develop them.
This article explores the role of software architects, outlining their responsibilities, essential qualities, differences between internet and traditional enterprises, team dynamics, common optimization practices, and practical advice on growing into an architect and advancing your career.
Meipai’s virtual‑item trading system, built to support over 100,000 daily live streams and millions of concurrent viewers, must process tens of thousands of requests per second while guaranteeing strong data consistency and high availability, and this talk by technical director Guo Chenhui explains the key design choices and trade‑offs employed.
This article explains Meitu's development of a distributed bitmap system that leverages the speed and storage efficiency of bitmap structures to handle massive user data, detailing its evolution, architectural choices, implementation practices, and lessons learned to inspire similar big‑data solutions.
This article introduces Meitu’s self‑developed log collection system Arachnia, explaining why a custom solution was needed for massive server‑side user‑behavior logs, the key requirements such as reliability and real‑time throughput, and the core architectural mechanisms that address those challenges.
This article explains what software architecture is, its lifecycle, why a solid architecture is crucial, how to distinguish good from bad designs, the roles and responsibilities of architects, and the skills—both technical and soft—needed to become an effective software architect.
The author shares a detailed, step‑by‑step account of preparing for and succeeding in multiple Silicon Valley software engineering interviews, covering personal motivation, interview types, practical tips, and a concrete study plan to help others secure similar offers.
This article distills essential guiding principles, high‑availability strategies, and high‑concurrency techniques for building resilient, scalable systems, covering stateless design, fault‑handling phases, replication, isolation, rate limiting, caching, async processing, multithreading, and scaling approaches.
The article outlines core guiding principles, high‑availability strategies, and high‑concurrency techniques—such as stateless design, replica and isolation, quota control, monitoring, degradation, rollback, and scaling—to help engineers build resilient, scalable web architectures for massive traffic.
This article explores the core concepts behind Twitter’s feed architecture, explaining how feeds and timelines are built from multiple lists, comparing push and pull notification models, discussing scalability constraints, and offering practical guidelines for choosing the right approach in large‑scale distributed systems.
Meituan‑Dianping’s payment team progressed from manual fault alerts to a fully automated channel management system that detects failures, disables affected banks, conducts controlled ramp‑up tests, and restores service, dramatically cutting response times, manpower costs, and secondary‑failure risks while boosting overall availability.
This article outlines essential principles for designing high‑concurrency and high‑availability systems, covering stateless architecture, service decomposition, caching strategies, message queues, data heterogeneity, degradation, rate limiting, traffic switching, rollback, and comprehensive business design rules such as idempotency, anti‑duplication, and documentation.
This article outlines essential high‑concurrency and high‑availability principles—including stateless design, service decomposition, caching strategies, message queues, data heterogeneity, degradation, rate limiting, traffic switching, and rollback mechanisms—to help architects build scalable, reliable, and resilient systems.
This article explores how product managers can decide between business‑oriented and technology‑oriented requirement‑analysis approaches for large‑scale IT systems, highlighting the trade‑offs, impact on user experience, and practical tips for combining both methods to build robust, user‑friendly solutions.
The article explains software architecture as a top‑down, macro view of systems—covering business decomposition, domain modeling, technical and system design, deployment considerations, and the skills architects need to create scalable, maintainable solutions.
This article completes and supplements the earlier “Architecture Design Principles” post by presenting the concepts, forms, and design principles of software architecture, accompanied by a full‑length PPT from a recent internal training session.
This article introduces the fundamental concepts, methods, types, goals, and product attributes of enterprise monitoring and alerting, explains the perspective differences between users and builders, and outlines a comprehensive monitoring system architecture for large‑scale operations.
The article explains that software architects focus first on server environment, concurrency, security, and quality attributes rather than UI layout, outlining key functional and non‑functional concerns, evaluation methods, and scaling strategies for systems such as MMOs.
This article explains software architecture as the composition and interaction of components, outlines its ANSI/IEEE definition, describes UML diagrams for modeling, discusses validation through testing, and shares practical development rules, offering a concise learning summary for engineers.
This article explains that an architectural style is a set of high‑level principles that provide an abstract framework for families of systems, discusses common styles such as client‑server, layered, pipe‑and‑filter, event‑driven, and REST, and examines their benefits, trade‑offs, and open design questions.
This article details Ctrip’s redesign of its real‑time user behavior service, covering the new architecture, data flow, use of Java, Kafka, Storm, Redis, and MySQL, and how it achieves high real‑time performance, availability, scalability, and fault‑tolerance to support massive travel‑industry traffic.
The article details Meituan’s overseas‑hotel backend system—from its initial construction using reusable services and mature frameworks, through custom micro‑service design emphasizing simplicity and extensibility, to extensive optimizations for availability, performance, and scalability, and finally team‑building practices that together ensure reliable evolution as business demands grow.
The article describes how Meituan‑Dianping built the Maze rule‑engine framework—comprising MazeGO for policy parsing and MazeQL for data queries—to replace hard‑coded and Drools‑based solutions, delivering hot‑deployed, versioned, pre‑compiled rules that lower maintenance cost, boost developer productivity, and enable non‑technical analysts to manage complex business logic efficiently.
The article discusses how expert programmers must continuously learn and balance humility with confidence, explores the end‑to‑end design principle, examines complexity, layering, and componentization in large systems, and highlights performance considerations, distributed‑system realities, and management lessons for building robust software.
The article shares real‑world examples of hidden risks in system design—such as unbounded buffers, concurrent map deadlocks, hash collisions, email floods, single points of failure, disk‑full issues, and cache miss overloads—and explains why early, thorough design thinking can prevent costly failures.
This article dissects the architecture of a flash‑sale (秒杀) system, outlining the typical e‑commerce flow, the unique characteristics of flash sales, the technical challenges of massive concurrent requests, and detailed solutions spanning isolation, static page delivery, CDN caching, dynamic URLs, request throttling, queue design, database sharding, caching strategies, overload protection, anti‑cheat mechanisms, and data safety techniques.
This article introduces five essential visual modeling techniques—mind maps, concept maps, system maps, mental models, and concept models—explaining their purposes, creation steps, and how they help designers and teams clarify ideas, organize understanding, and communicate complex systems effectively.
This article describes the design, architecture, and operational features of Baidu Waimai's unified voucher issuance platform, detailing its four‑layer backend structure, permission and strategy configurations, flow‑control mechanisms, service isolation, monitoring visualizations, and re‑entrancy safeguards to support large‑scale marketing distribution.
The article explores whether effective software architecture stems from upfront design or gradual evolution, presenting viewpoints from senior architects, discussing stakeholder concerns, non‑functional requirements, real‑world evolution cases like 58.com and Google, and urging readers to share their own conclusions.
The article analyzes the rapid growth‑induced technical debt of a sales platform and details a multi‑layered architectural optimization—including data‑layer redesign, monolith decomposition, and service‑oriented transformation—while discussing associated challenges and future service‑governance improvements.
This article examines essential concepts such as modules, components, patterns, and layers, outlines common layering schemes, and details both runtime and source‑code organization considerations—including requirements compliance, performance, manageability, security, reliability, extensibility, portability, and documentation—to guide effective software architecture design.
This article explains software architecture styles as high‑level design principles that guide system families, outlines common styles, their benefits and drawbacks, discusses open design questions, and provides detailed examples such as client‑server, layered, pipe‑filter, event‑driven, repository, C2, three‑tier, JB/HMB, and REST architectures.
This article outlines a comprehensive software architecture design workflow—including business analysis, solution and system design, architectural patterns, data distribution strategies, integration models, and interface design—to help architects build robust, scalable enterprise systems.
This article recounts the author's personal journey from a graduate working in government to a senior architect at global tech firms, highlighting the evolution of software architecture, essential qualities for architects, and practical advice for aspiring architects to develop breadth, depth, and strategic vision.
The author announces a forthcoming series on Internet high‑availability architecture, outlining topics such as CAP theory, distributed caching, SOA, message queues, search systems, and real‑world case studies, and invites readers to suggest additional content while promising detailed, valuable guidance for developers and architects.
This article explains what high availability means for distributed systems, outlines common availability tiers, and describes how redundancy, load balancing, and automatic failover across a typical Internet architecture can achieve reliable, scalable services.
This article explains what software architecture means, outlines a step‑by‑step approach to designing an architecture that aligns with business needs, describes the key characteristics of a good architecture, highlights common misconceptions, and offers concluding advice for aspiring architects.
This article surveys the design of end‑to‑end tracing systems for large distributed services, explaining core use cases, tracing approaches, metadata propagation, sampling strategies, visualization techniques, and recommended design choices to improve debugging, performance analysis, and resource attribution.
As microservice architectures grow, service calls become increasingly complex, involving dozens of services and teams, making rapid fault localization and comprehensive data analysis critical; distributed tracing systems address these challenges by providing end‑to‑end visibility, low‑overhead instrumentation, and scalable monitoring across large‑scale applications.
This article explains the essence of software architecture, outlines key project roles, details the duties and workflow of architects, and maps out a clear growth path and competency model for aspiring architects.
This article compiles 99 practical principles and habits—from communication and decision‑making to performance, scalability, and team leadership—that every software architect should understand and apply to build high‑quality, maintainable systems and advance their career.
This article explains the layered architecture of a web system, covering flexible component choices, load‑balancing techniques, business service and communication layers, various storage options—including file, block, and object storage—and key evaluation criteria for building robust, cost‑effective solutions.
This article outlines a comprehensive series that guides developers and aspiring architects through the fundamentals, career path, modeling techniques, design patterns, deployment strategies, and real‑world case studies of software architecture, offering a step‑by‑step roadmap for growth.
This article explains software architecture as the arrangement and interaction of components, outlines its standards, discusses UML diagrams for modeling, describes the role of architects, and shares practical rules for effective system design and development.
This article explains UML as a modeling language, detailing its semantics and notation, and introduces the nine core diagram types—use case, class, object, static, behavior, interaction, implementation, component, and deployment—highlighting their purposes, differences, and how they support static and dynamic system modeling.
This article details Shanda Games' journey in designing and implementing a comprehensive automated operations platform—including installation, deployment, security, client and server updates, data analysis, backup, and monitoring—to efficiently manage hundreds of games across diverse hardware and operating systems.
This article examines common misconceptions in designing geo-distributed active-active systems, explains why striving for perfect real-time data sync is unrealistic, and offers practical strategies—such as prioritizing core services, reducing distance, limiting data replication, and combining storage sync with messaging—to achieve reliable high-availability.
This article explains the comprehensive concept of high‑availability systems, covering redundancy, failover, consistency challenges, various technical solutions, SLA definitions, and the organizational and engineering practices required to achieve multiple “9s” of availability.
This article outlines the concepts, classifications, and detailed backend design of a message/notification system, including architecture, database schemas, subscription mechanisms, push/pull strategies, and service-layer APIs for creating, pulling, and managing announcements, reminders, and messages.
This article shares practical anti‑crawling concepts, classifications of crawlers, design principles, traditional and JavaScript‑based countermeasures, and operational trade‑offs, illustrating how Ctrip's hotel R&D team balances commercial protection with technical feasibility.
The article reflects on a misleading interview about aspiring architects, critiques duplicated logic and tight coupling in enterprise systems, and argues that a true software architect should provide holistic design, reduce redundancy, and possess both technical and coordination skills.
This article details the architectural design and implementation of a scalable big data platform built on AWS services, highlighting the transition from HDFS to S3 for storage, the use of EMR for elastic compute, and a custom Execution Service integrated with Consul and Airflow for automated cluster management and task scheduling.
Service overload caused by cache failures can cripple dependent systems, but by adopting smart cache get patterns, proactive client‑side checks, traffic throttling, service degradation, and dynamic scaling, developers can both prevent overload and recover gracefully when it occurs.
This article chronicles Meituan's payment channel gateway evolution—detailing early usable stages, subsequent availability improvements, and the implementation of a flexible, fault‑tolerant architecture that achieved 99.99% API uptime and record‑high transaction throughput.
The article shares practical experiences from refactoring three backend systems—M, S, and X—highlighting the challenges of keeping business running while redesigning architecture, the concrete solutions applied, measurable outcomes such as increased release frequency and higher availability, and key lessons on prioritizing problems and avoiding over‑refactoring.
The article outlines how to effectively tackle extensive architecture refactoring by prioritizing issues, classifying them, and implementing a phased strategy that focuses limited resources on specific problem categories to achieve clear, incremental results and maintain team morale.
This article explores the definition, lifecycle, importance, and best practices of software architecture, compares good and bad designs, outlines the roles and responsibilities of architects, and offers guidance on the skills and mindset needed to become an effective software architect.
This article analyzes flash‑sale (抢购) business scenarios, outlines a layered architecture separating business and data layers, explains decoupling front‑end pressure, uses Redis‑based queues and caching to manage high‑frequency inventory checks, and describes multi‑party reconciliation mechanisms to ensure reliable stock consistency under extreme load.
This article shares eBay’s seven core scalability best practices—including functional partitioning, horizontal sharding, avoiding distributed transactions, asynchronous decoupling, stream processing, virtualization, and smart caching—to help architects design highly available, cost‑effective systems that can handle billions of daily requests.
The article explores the philosophical and practical aspects of software architecture, describing its essence as reducing system entropy through modular decomposition and recombination, outlining architecture classifications, the architect’s skill set, and the four stages of architectural mastery, all illustrated with real‑world examples.
Over eight years of building and evolving a service framework, the author reflects on fourteen critical design mistakes—from intrusive XML configurations and poor technology choices to insufficient versioning, load‑balancing flaws, and inadequate monitoring—highlighting the importance of comprehensive, forward‑looking architecture for backend engineers.
This article explores the critical role of a software architect, detailing the essential business understanding, abstraction, coding ability, comprehensive system thinking, global impact awareness, and trade‑off decision‑making skills required to excel in the position.
This article shares Tencent’s experience building fault‑tolerant mechanisms for the AMS activity platform, covering retry strategies, automatic machine exclusion, timeout tuning, service isolation, asynchronous processing, anti‑replay safeguards, and operational best practices that transformed a million‑request service into an 800‑million‑request system.
The article describes a three-dimensional, automated, visual monitoring approach for high-availability systems, detailing a five-layer monitoring model, automated log collection using Logstash-Redis-Elasticsearch, and visualization techniques that together reduce fault-locating time and improve operational efficiency.
The article explains how functional separation and degradation techniques—distinguishing core from non‑core services, isolating them logically and physically, and implementing manual or automatic fallback mechanisms—help maintain high availability in distributed systems during traffic spikes or component failures.
The article outlines the essential qualities, responsibilities, and decision‑making principles of a software architect, emphasizing business understanding, comprehensive system design, technical depth, global perspective, and balanced trade‑offs to ensure scalable, maintainable, and future‑proof solutions.
In this interview, chief architect Wang Fuqiang shares the essential qualities of a successful software architect—forward‑looking vision, systematic thinking, an open mindset, and continuous learning—illustrated with real‑world examples and practical advice for building sustainable, high‑value systems.
The SDCC 2015 Architecture Session recap presents practical insights from industry experts on how major Chinese internet companies transformed their systems to handle rapid growth, high availability, scalability, and performance through progressive refactoring, service‑oriented architectures, and modern infrastructure practices.
Facing high maintenance costs, complex business demands, and costly Microsoft tech, a company migrated its five‑year‑old transaction platform to Java, employing phased refactoring, comparative testing, and traffic‑splitting to ensure correctness, minimal impact, and a smooth, zero‑downtime rollout with centralized configuration and logging.
This article summarizes Chen Ming’s 2015 ArchSummit talk on WeChat Moments, detailing its massive posting volume, core database tables, publishing and reading workflows, and the multi‑data‑center disaster‑recovery architecture that ensures seamless, loss‑less service worldwide.
The article shares a former Google SRE’s insights on building high‑availability systems, explaining key factors such as MTBF and MTTR, redundancy strategies like N+2, change‑management practices, and practical tips for reliability engineering and operations.
The article explores the evolving role of software architects in the internet era, outlining their core responsibilities, essential capabilities, and four key practices—broad information gathering, compromise, taking responsibility, and confronting conflict—to guide professionals toward effective system design and continuous growth.
The article chronicles a developer’s journey from a simple personal homepage to managing billion‑visit web platforms, sharing practical insights on architecture evolution, knowledge structures, design principles, infrastructure, and software engineering practices essential for building and operating large‑scale websites.
This article explains the design and implementation of an operations automation platform, covering the necessity of standardization, system architecture, module functions, database modeling, work‑order processes, and real‑world examples to help IT teams achieve efficient, reliable, and low‑risk operations.
The article defines a software architect as a senior engineer responsible for high‑level system design, explains the role’s core value in breaking large systems into low‑coupled modules, and outlines six essential abilities and four practical lessons for effective architectural practice.
This article explains how to architect a high‑traffic flash‑sale system by separating data and business layers, using Redis queues for inventory consistency, and implementing multi‑party transaction reconciliation to handle massive concurrent requests while maintaining reliable stock information.
Designing a short URL service involves choosing appropriate key‑value storage, simple incremental or base‑36 encoding for keys, estimating data capacity and sharding strategies, handling concurrent reads/writes with thread‑safe structures or Redis, selecting network event loops, and addressing security concerns such as abuse prevention.
A former EE PhD turned chip engineer shares his interview journey, detailing recruiter outreach, phone screens, and onsite challenges across Facebook, LinkedIn, and Google, while listing the algorithmic and system‑design problems he faced.
