The article shares a senior Alibaba engineer’s reflections on what architecture means, the architect’s role, essential skills, and the challenges faced, offering practical insights for developers aspiring to become effective software architects.
Drawing on years at Alibaba, the author shares insights on top‑level design, physical and application architecture, the evolving role of architects, and the essential skills—problem discovery, definition, solution, communication, breadth, and continuous learning—required to tackle complex, global system challenges.
This article explains the full design of a marketing automation system—from requirement analysis and essential capabilities to a four‑layer architecture, FSM‑based engine model, execution strategies, and key modules such as state control, time control, event rule processing, action execution, monitoring, exception handling, and data warehousing—providing a practical blueprint for developers.
This article explains the fundamentals of software architecture diagrams, outlines the purpose and classification of different diagram types, describes common pitfalls, and provides a step‑by‑step guide to using the C4 model—including system context, container, component, and class diagrams—plus a real‑world case study.
This article explains the definitions of domain and data models, illustrates why they are often confused, shows real‑world examples of misusing each, and provides practical guidance on separating them to improve system design, scalability, and maintainability.
Designing a distributed system involves overcoming major challenges such as heterogeneity, transparency, openness, concurrency, security, scalability, and fault tolerance, each requiring careful consideration of hardware, software, network, and management aspects to build robust, scalable, and secure architectures.
The article humorously maps various relationship scenarios to core IT concepts such as backup strategies, high‑availability mechanisms, scaling methods, security measures, cloud services, and big‑data techniques, providing an engaging overview of fundamental system design principles.
This article details how the L‑D stage of international hotel pricing was optimized through a new offline‑fetch scheduling mechanism, cache‑freshness calculations, and a comprehensive refactor of the rebuild system, resulting in lower latency, higher throughput, and a smoother user experience.
The article explains high availability as a source of system complexity, describing how redundancy, hardware and software failures, external disasters, and state‑decision mechanisms such as dictatorial, negotiated, and democratic approaches affect both compute and storage layers, and discusses trade‑offs like the CAP theorem.
This article explains how to design a flash‑sale (seckill) system that handles massive concurrent reads and writes by applying principles such as minimizing data and request volume, shortening request paths, eliminating single points of failure, and employing layered caching, traffic shaping, and robust high‑availability strategies.
Cache leverages the space‑time trade‑off to boost performance, but introduces complexity; this guide explains its fundamental idea, local vs distributed solutions, popular Java caching libraries, and key read/write patterns such as Cache‑Aside, Read‑Through, and Write‑Behind, highlighting benefits, drawbacks, and best‑practice considerations.
This article outlines a comprehensive knowledge framework for software architects, covering nineteen essential areas such as responsibilities, foundational concepts, internet system challenges, distributed caching, messaging, load balancing, performance testing, operating systems, algorithms, networking, database design, JVM internals, flash-sale systems, microservices, domain‑driven design, security, high‑availability, big data, and blockchain.
This article examines common misconceptions about software architecture, explains that its core purpose is to manage system complexity, offers practical guidance for identifying complexity hotspots, and presents a concrete university student‑management system case study to illustrate effective architectural decision‑making.
This article introduces ten widely used software architecture patterns—including layered, client‑server, master‑slave, pipe‑filter, broker, P2P, blackboard, interpreter, and MVC—explaining their structures, typical use cases, advantages, and disadvantages, and provides a comparative table to help developers select the most suitable pattern for enterprise‑level system design.
This article demystifies software architecture by defining systems, subsystems, modules, components, and frameworks, illustrating their relationships with real‑world examples and diagrams, and proposing a concise definition of architecture as the top‑level structure of a software system.
This article explains the principles, data models, storage choices, synchronization strategies, metadata handling, and scaling considerations for building a high‑performance feed‑stream system that can support millions to billions of users, with practical guidance on using NoSQL or relational databases.
The article analyzes flash‑sale (秒杀) business characteristics, outlines the technical challenges of massive concurrent requests, and presents architectural principles, backend design, database strategies, concurrency control, anti‑cheat measures, and practical code examples to build a reliable high‑throughput system.
Drawing from NetEase Yanxuan’s experience, the article outlines three universal B2B design principles: define clear system boundaries and ownership, enforce order through universal interaction rules as scale grows, and prioritize abstract rule‑based capabilities over mere process digitization to create scalable, adaptable solutions.
This article explains the essence of software architecture, outlines its various classifications—including business, application, technical, code, and deployment architectures—describes when architecture design is needed, and presents metrics and common pitfalls for evaluating a sound, scalable system.
This comprehensive guide outlines the philosophical mindset, core competencies, technical knowledge, architectural principles, and essential tools that aspiring software architects should master to build robust, scalable, and secure systems in modern IT environments.
The article outlines the essential competencies—technical mastery, business understanding, design foresight, depth and breadth of knowledge, communication, and systematic thinking—that a software architect must develop to effectively lead and deliver complex projects within an organization.
The article explains what a software architect is, outlines their evolving responsibilities across development phases, describes various architect specializations, highlights essential skills and team collaboration practices, and offers career guidance for aspiring architects.
The article presents a comprehensive set of fifteen universal software architecture principles—ranging from redundancy and rollback to automation and non‑intrusive design—along with essential design guidelines such as separation of concerns, single responsibility, and low coupling to help architects build scalable, reliable, and maintainable systems.
This article systematically explains monitoring fundamentals, the seven core functions of a monitoring system, proper usage practices, common monitoring objects and metrics, the basic data flow, and provides detailed comparisons of three popular open‑source solutions—Zabbix, Open‑Falcon, and Prometheus—to guide informed selection decisions.
This article explains how to conduct thorough requirement analysis, classify and prioritize needs, and translate them into solid software architecture decisions, highlighting demand capture, functional, quality, and constraint considerations, as well as practical steps for prioritization and implementation.
This article presents a thorough exploration of system design and architecture, covering core concepts, thinking models, analysis techniques, design processes, modeling methods, TOGAF framework, and practical tools to help architects transform complex business requirements into clear, implementable system solutions.
This article introduces ten widely used software architecture patterns, explains their purposes, advantages, disadvantages, and typical application scenarios, and provides a comparative table to help developers choose the most suitable architecture for large‑scale enterprise systems.
This article explains the 4+1 view model for software architecture, detailing its logical, process, development, and physical views, how scenarios tie them together, and why using multiple concurrent views improves design, documentation, and risk management in large‑scale systems.
This comprehensive guide explains the essence of software architecture, clarifies related concepts such as systems, modules, and frameworks, and details various architectural layers, classifications, evolution paths, and best‑practice considerations for building robust, scalable systems.
This article explains how to design a high‑performance feed‑stream system—covering product definition, data categories, storage options, synchronization modes, metadata handling, commenting, likes, search, sorting, deletion, and update—so you can build a solution that scales to millions or billions of users.
This comprehensive guide explains what software architecture is, distinguishes systems, subsystems, modules, components, and frameworks, outlines architecture layers and classifications, describes strategic versus tactical design, tracks the evolution from monoliths to micro‑services, and highlights how to evaluate and avoid common architectural pitfalls.
This article explains the fundamental concepts of software architecture, distinguishes systems, subsystems, modules and components, describes various architectural layers such as business, application, data, code, technical and deployment, outlines evolution from monoliths to micro‑services, and highlights common misconceptions and measurement criteria for a sound architecture.
This comprehensive guide walks you through the fundamentals of system design, covering core concepts, analytical thinking, modeling techniques, architecture classification, design tools, and best‑practice principles to help you build robust, scalable software systems.
Microservices aren’t a universal solution; this article outlines five common situations—insufficient complexity, small teams, indivisible applications, legacy system integration, and tight real‑time integration—where adopting a microservice architecture can add unnecessary overhead and risk, advising developers to choose the right architecture for their needs.
In a Cloud+ community salon, three Tencent Cloud senior engineers dissect the three‑stage evolution of software architecture—from monolithic to distributed to AI‑driven—share the iterative design of Tencent Cloud Disk, outline request‑centric high‑availability metrics, advise systematic project takeover, and stress hands‑on learning, proactive incident response, and future‑ready practices while inviting talent to join.
This article explains the principles and practical techniques for achieving high availability, scalability, isolation, decoupling, rate limiting, degradation, and circuit breaking in modern software systems, providing concrete examples, algorithms, and deployment patterns to improve reliability and performance.
This article explores the fundamentals of distributed systems, explaining what they are, why they’re used, design considerations such as replication and partitioning, the implications of the CAP theorem, common distribution strategies, typical architectural patterns, and the advantages and challenges of building and operating such systems.
This article explains the definitions and differences of QPS and TPS, how they relate to concurrency and system throughput, and introduces related metrics such as PV, UV, DAU, response time, and practical considerations for performance testing and capacity planning.
This article explains the fundamental concepts of software architecture, including definitions of systems, modules, frameworks, various architectural layers such as business, application, data, code, technical and deployment, and discusses the evolution from monolithic to distributed and microservice architectures along with evaluation criteria and common pitfalls.
This article explains the fundamental concepts of software architecture, distinguishes system, subsystem, module, component, and framework, outlines architectural layers and classifications, describes the evolution from monolithic to distributed and micro‑service architectures, and discusses how to evaluate and avoid common design pitfalls.
This article presents a comprehensive design of a flash‑sale system, covering business scenario analysis, high‑concurrency problems such as overselling and malicious requests, and detailed front‑end, Nginx, risk‑control, back‑end, database, and distributed‑transaction solutions to ensure reliability and performance.
This event features an architect from JD.com's backend team discussing strategies for designing high-availability, high-performance order systems to handle massive concurrent orders during major sales events like 618, based on real-world case studies and Elastic technology implementations.
This article explains how software architects can use UML‑based modeling and a series of design documents to capture domain problems and system solutions, communicate functional and non‑functional requirements, and guide development across requirement analysis, architectural design, and detailed implementation.
This article explains the concept of loose coupling in banking IT systems, outlines its definitions, measurement criteria, and practical design guidelines across components, interfaces, data, and processes, while also discussing the trade‑offs and costs associated with adopting a loosely coupled architecture.
This article systematically introduces the advertising transmission process, outlines challenges of scale and stability, and presents a comprehensive set of architectural, operational, and performance optimizations—including primary‑backup high availability, stateless incremental processing, message reliability, flow tiering, indexing sharding, and schedule management—to achieve high‑throughput, low‑latency, and eventually consistent ad delivery.
This article details Youku's membership marketing system architecture, covering complex marketing scenarios, high‑availability and low‑latency requirements, rule‑based QL engine, unified marketing framework, multi‑cache storage, multithreaded matching, asynchronous reward distribution, and distributed transaction mechanisms.
This article explains the challenges of generating globally unique IDs in sharded databases, compares common solutions such as auto‑increment, UUID, Snowflake, and Redis, and presents a practical MySQL‑based design that uses table‑level auto‑increment combined with in‑memory segment allocation to achieve high concurrency, reliability, and performance.
Tellus, a user‑and‑item task system for Xianyu’s lightweight publishing, guides sellers to complete missing item details or adjust prices by decoupling task creation via MetaQ, storing billions of records in Table Store, and offering configurable, template‑based tasks that have doubled completion rates and accelerated feature rollout.
This article explains how to handle session sharing in distributed systems through replication, sticky sessions, or a dedicated session server, and addresses cache penetration and avalanche issues with practical mitigation techniques such as request filtering, empty-object caching, hash repositories, Redis clustering, staggered expirations, and concurrency controls.
This article explains the concept of distributed architecture, its evolution from monolithic systems, core design principles, common challenges such as network latency and data consistency, and how major tech companies adopt it to achieve high availability, scalability, and fault tolerance.
Distributed architecture, built on distributed computing technologies like J2EE, transforms monolithic systems into multi‑layer, fault‑tolerant platforms by decoupling services, ensuring high availability, scalability, and resilience, while addressing challenges such as network latency, data consistency, and system complexity, as illustrated by real‑world case studies.
This guide explains practical techniques—service splitting, caching, message queues, database sharding, read/write separation, and Elasticsearch—to design high‑concurrency back‑end systems that impress interviewers and handle real‑world traffic spikes.
This article introduces the concept, core capabilities, and architectural evolution of a reconciliation center—from its initial 1.0 design through 2.0 and 3.0 upgrades—highlighting problem statements, solution approaches, and the applicable scenarios that make it essential for large‑scale data consistency in modern micro‑service systems.
After two months of intensive development, the team launched a new monitoring and alerting platform that transforms a legacy system into a service‑oriented solution, addressing pain points such as inflexible escalation, noisy alerts, and poor ownership while introducing phone alerts, automated escalation, Prometheus integration, and a unified rule engine.
This article explains the design and implementation of the Haishen crash monitoring platform for iOS, covering its system architecture, data collection, parsing, aggregation, routing, SDK features, exception handling, stack capture, startup crash detection, and upload mechanisms to quickly expose, locate, and fix crashes.
The article walks through a candidate’s full Google engineering interview experience—including recruiter screening, phone coding rounds, onsite technical sessions, system‑design challenges, and interview logistics—while offering practical tips and resources to help future applicants prepare effectively.
This article explains what an architecture diagram is, why it matters, and provides a step‑by‑step methodology—including business and system modeling, abstraction techniques, and evaluation criteria—to help engineers create clear, purposeful diagrams for diverse stakeholders.
This article explains what an architecture diagram is, why it matters, and provides a step‑by‑step methodology—including business and system modeling, abstraction techniques, diagram classification, drawing guidelines, and quality evaluation—to help engineers produce clear, purposeful diagrams that improve communication and collaboration.
This article explains what an architecture diagram is, why it’s essential for communication and efficiency, and provides practical guidance on defining architecture, modeling processes, abstraction techniques, drawing methods, evaluation criteria, and the role of an architect in software development.
The logistics R&D team spent 62 days preparing for the 618 promotion by analyzing core processes, applying stress tests, implementing fault‑tolerant architectures, planning capacity, and deploying real‑time monitoring tools to ensure system stability and performance under peak traffic.
This article provides a thorough overview of distributed systems, explaining their definition, core challenges, key characteristics, essential components, common protocols, and practical implementations to help readers build a solid, structured learning path for mastering distributed architectures.
This article examines Meituan's evolution from hard‑coded validation to a custom rule‑engine framework, detailing case studies of store information checks, audit workflows, and performance metric calculations, and explains the design of the Maze framework that separates business logic from system code while improving maintainability and scalability.
The article outlines the historical evolution of IT architecture—from early single‑machine deployments through hot‑standby and multi‑node active clusters to modern distributed systems—explaining the motivations, trade‑offs, and key technologies that drive each generation and offering guidance on selecting the right architecture for business needs.
This article presents John Washam's comprehensive, now Chinese‑translated guide covering programming language choices, hardware basics, algorithm and data‑structure fundamentals, flashcard study methods, interview résumé tips, common Google interview questions, and additional efficiency tools, all aimed at helping engineers prepare for Google interviews.
This article explains why clear architecture diagrams are essential for effective communication, outlines common pitfalls when drawing them, defines architecture and its diagram types, introduces the C4 modeling approach, and provides concrete examples and best‑practice tips to create self‑describing, audience‑focused diagrams.
This comprehensive article explains the essential concepts of software architecture, including definitions of systems, subsystems, modules, components, frameworks, and architecture itself, and then details various architectural layers such as business, application, data, code, technical, and deployment, while also covering evolution from monoliths to micro‑services and common pitfalls.
This article explains the purpose and benefits of software architecture diagrams, defines key concepts such as architecture and diagram types, outlines common pitfalls, introduces the 4+1 and C4 modeling approaches, and provides practical guidance and examples for producing clear, audience‑focused diagrams.
This article explains why clear architecture diagrams are essential for communication, defines core concepts, categorizes diagram types, outlines common pitfalls, and introduces the C4 model with practical tips to create self‑describing, audience‑focused diagrams that align with code.
This article presents a collection of interview questions and resource links covering system design, distributed sessions, Java pitfalls, MySQL indexing, and other backend topics, encouraging developers to keep learning and offering QR code access for further content.
This article explains the fundamental concepts of software architecture, distinguishes systems, subsystems, modules, components, and frameworks, outlines various architecture layers and classifications, describes architecture levels, tracks the evolution from monolithic to micro‑services, and discusses how to evaluate and avoid common architectural pitfalls.
This article outlines how to create solid software architectures by presenting a process for forming design principles, detailing fifteen universal architecture guidelines, and explaining service‑splitting and key design rules that together help build scalable, maintainable, and resilient systems.
This reading note explains the definition of architecture, its three essential elements, the role of an architect, how to distinguish problems, means and challenges, and how model‑thinking complements architectural thinking through concrete examples and classic models such as the cognitive pyramid and the Solow growth model.
This article explains the hierarchical architecture levels, contrasts strategic and tactical design, and walks through the evolution from monolithic applications to distributed services and micro‑services, highlighting benefits, drawbacks, and key metrics for evaluating a sound system architecture.
This article outlines frequent software architecture misconceptions, traces the evolution of large‑scale system designs, presents core architectural patterns and essential elements, and recommends key books to help engineers create high‑performance, reliable, and secure applications.
This article explains the fundamental definition of software architecture, distinguishes related concepts such as system, subsystem, module, component, and framework, and outlines the various architectural layers—including business, application, data, code, technical, and deployment—while highlighting the architect's responsibilities and when architecture design is needed.
The article examines how financial platforms can acquire user accounts, design fast‑perceived business experiences through account mapping, capital advances, and cross‑account interoperability, and build stable, high‑performance backend and transaction systems that balance compliance, user experience, and operational costs.
Clear, layered software architecture diagrams prevent misunderstandings, and the C4 model—covering Context, Container, Component, and Code levels—offers a simple, universal language for visualizing static system structures, guiding teams from high‑level overviews to detailed code maps across diverse audiences.
This comprehensive guide explains the true essence of software architecture, covering definitions, system vs. subsystem, modules vs. components, frameworks vs. architecture, various architectural layers (business, application, data, code, technical, deployment), evolution from monolith to microservices, common pitfalls, and recommended reading, all aimed at helping architects design suitable, efficient, and maintainable systems.
The article outlines five key layers—front‑end optimization, middle‑layer load distribution, gateway control, service‑layer improvements, and database tuning—detailing practical techniques such as static resource caching, Nginx load‑balancing methods, request rate limiting, message‑queue buffering, and extensive MySQL best‑practice guidelines to build robust high‑concurrency architectures.
The article shares practical insights from a year‑long experience in an internet company, comparing the work attitudes, technical foundations, and responsibilities of architects versus senior developers, and offers concrete steps and resources for engineers aiming to upgrade to an architect role.
This article explains how to design a high‑performance, highly available flash‑sale system by applying dynamic/static separation, hotspot optimization, inventory reduction strategies, and comprehensive high‑availability engineering, covering both architectural principles and concrete implementation details.
This article explores what a software architect does, defines the role, outlines three architectural levels, details daily responsibilities, and breaks down ten essential skills—including design, decision‑making, simplification, programming, and documentation—to help engineers become better architects.
The article outlines Youzan's retail finance middle platform design, detailing the business background of complex SaaS retail, a structured analysis using layered business, application, data, and technology architectures, and a step‑by‑step implementation that emphasizes reusable domain capabilities and long‑term, standardized middle‑platform development.
The author recounts eight interview experiences across companies like Afanti, XueTang Online, Guokr, Veeva, Zhihu, Spring Rain Doctor, 360, and Toutiao, sharing detailed insights on Python fundamentals, network protocols, system design, database concepts, and personal lessons that helped secure a final offer.
The article explains a software architect's core duties, contrasts them with developers, outlines how to become an architect, and provides practical advice on topics such as UML, Spring Cloud vs Dubbo, distributed tasks, high concurrency, rate limiting, data synchronization, and large‑scale data updates.
This article explains the role of message‑queue middleware in distributed systems, covering its communication patterns, ten key advantages such as decoupling and scalability, and practical use cases like asynchronous processing, traffic shaping, log handling, and e‑commerce architectures.
This article describes Alibaba‑Mama’s research on improving click‑through rate (CTR) prediction by modeling users’ long‑term interests with incremental computation services, memory‑network architectures (MIMN and HPMN), system redesign (UIC and RTP), and extensive offline and online experiments that demonstrate significant GAUC and CTR gains.
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 explains how to design a flash‑sale (秒杀) system that handles massive concurrent requests by applying dynamic‑static separation, hotspot optimization, database tuning, and traffic‑shaping techniques to achieve high performance, strong consistency, and robust high‑availability.
This guide outlines the duties of a software architect, the essential technical and soft‑skill competencies required, a detailed technology stack covering collections, frameworks, security, JVM, concurrency, databases, big data, and distributed systems, and provides a curated learning‑material package for aspiring architects.
This article recounts Huang Jie’s presentation on the evolution of Ele.me’s monitoring system, detailing its three development stages, the challenges faced, the layered monitoring architecture, the design of a unified platform supporting both PC and mobile, and the underlying LinDB time‑series database.
This article explores the architectural design of a flash‑sale (秒杀) system, covering high‑performance techniques, consistency guarantees, high‑availability strategies, hotspot optimization, and practical implementation details such as static‑dynamic separation, caching, data integration, and database tuning.
This article explains the design of a high‑concurrency train‑ticket flash‑sale system, covering distributed load‑balancing, Nginx weighted round‑robin, local and remote stock deduction, Go implementation, Redis atomic scripts, and performance testing with ApacheBench.
This article reflects on the redesign of a large‑scale transaction system, describing a decision‑making routine that starts from purpose and goals, discusses programming paradigms, SOLID principles, domain‑driven design, bounded contexts, component splitting, layering, and the trade‑offs of patterns such as State and CQRS to achieve a flexible, maintainable backend architecture.
The article argues that simple, term‑free design processes—focused on business problems, whiteboard brainstorming, concise documentation, and iterative feedback—outperform formal architecture tools, patterns, and dedicated architects in large‑scale systems like Uber, emphasizing engineering culture over rigid methodologies.
The article explains how leading tech companies like Uber and Skype design massive systems using simple, informal diagrams and collaborative documentation instead of formal architecture tools or dedicated architects, emphasizing simplicity, team autonomy, and practical trade‑offs over rigid patterns.
This article explains what technical architecture is, breaks down its three core components—business technical problems, technical solutions, and technical components—and then dives deep into high‑concurrency challenges, systematic thinking methods, and practical approaches such as resource scaling, stateless design, load balancing, caching, and I/O optimization.
This article explains the essence of scalability as a placeholder concept, outlines a four‑step method—standardize, identify, register, use—and demonstrates its application through Java SPI and a coupon platform case study to design extensible backend systems.
This article explains why and how to isolate business lines and platforms, use product IDs for separation, create visual capability maps, employ mock data for issue reproduction, and implement monitoring to improve communication, efficiency, and rapid problem detection in large-scale systems.
After six months of studying MySQL, Redis, and distributed systems, I tackled a Go backend engineer interview at Tencent, detailing the questions on networking, databases, OS concepts, system design, and my reflections on what to improve for future interviews.
