The article outlines the objectives, detailed call flow, architectural components, and potential issues of a payment center system, describing how unified order, payment, and financial services are built, integrated with third‑party channels, and managed through modules such as backend, messaging, transaction core, and channel gateway.
This article outlines a thorough methodology for evaluating software, hardware, and overall system architectures, detailing assessment criteria, a five‑stage evaluation process, quality‑assurance measures, and best‑practice checkpoints to ensure high availability, scalability, security, and cost‑effectiveness of complex engineering projects.
This article explains how to design and evaluate system capacity by defining key concepts such as design capacity, TPS, QPS, and concurrency, outlining when capacity assessment is needed, and providing a step‑by‑step methodology with real‑world examples and calculations for accurate performance planning.
The article outlines the essential duties, required competencies, decision‑making principles, and optimization techniques for software architects, covering system decomposition, technology selection, communication, technical depth, performance tuning, database scaling, and the broader mindset needed to lead complex development projects.
The article analyzes Bilibili’s recent service outage, explains why high availability matters, introduces key metrics like MTBF and MTTR, and outlines practical strategies such as redundancy, rate limiting, isolation, failover, timeout control, circuit breaking, degradation, and multi‑region deployment to build resilient systems.
This article explains the benefits of short URLs and presents a comprehensive, interview‑friendly design for a high‑performance short‑link service, covering redirect mechanics, hash‑based and auto‑increment generation methods, database schema, collision handling, and an OpenResty‑based architecture for massive concurrency.
This article explains the drawbacks of traditional synchronous architectures, outlines why adopting message queues improves latency, coupling, and peak‑handling, and then details common MQ problems such as duplicate messages, data inconsistency, loss, ordering, backlog, and increased complexity along with concrete mitigation strategies.
This article explains the five architectural views—logical, development, runtime, physical, and data—clarifies the distinction between software and system architecture, discusses tier versus layer concepts, outlines the benefits of logical and physical layering, and describes the various kinds of architects and their responsibilities.
The article explains why message queues are essential for decoupling systems, improving latency, handling traffic spikes, ensuring high availability, maintaining order, and achieving idempotent consumption, while also discussing their disadvantages, configuration details for Kafka, RabbitMQ, RocketMQ, and practical troubleshooting strategies.
The article describes Xianyu’s local services architecture, tackling rapid supplier onboarding, heterogeneous quality, and stability by reusing core platform capabilities, defining merchant, audit, and independent business domains, employing high‑concurrency rate limiting, idempotent retries, unified exception handling, status‑change logging, and proactive monitoring with alerts and reporting.
This article analyzes various high‑availability strategies for stateful backend services—covering cold backup, dual‑machine hot standby, same‑city active‑active, remote active‑active, and multi‑region active‑active architectures—detailing their benefits, limitations, and practical implementation considerations.
This article explains the evolution of software architecture styles, defines architecture domains, and presents a detailed classification table covering web, rich client, mobile, integration, data, modeling, and analytics architectures, followed by community promotion details.
This article outlines the concepts, advantages, drawbacks, and design guidelines of layered architecture, explores logical, presentation, service, and physical layers, and demonstrates a Java implementation with detailed diagrams to help developers build scalable, maintainable systems.
The article explains software architecture by distinguishing the business and computer problems it must solve, outlines the responsibilities of owners and engineers, and describes how increasing scale leads to layered deployment, code, and organizational structures.
This article explores the origins of software as a human‑simulation tool, examines how cost reductions and technological advances have driven its widespread adoption, and explains how increasing complexity led to the emergence of specialized roles and architectural practices in modern software development.
This article explains the fundamental concepts of software architecture—including systems, subsystems, modules, components, frameworks, and architecture itself—by defining each term, illustrating their relationships with real‑world examples, and clarifying common misconceptions for technical professionals.
This article examines the purpose of software architecture by identifying its diverse stakeholders, detailing the refinement process, illustrating the 4+1 view model with diagrams, outlining documentation practices, summarizing key takeaways, and previewing the next installment on deployment architecture.
This article clarifies core web‑service metrics—QPS, TPS, PV, UV, DAU, MAU—explains their differences, shows how concurrency and throughput relate, and outlines key performance‑testing concepts and evaluation methods for modern system capacity planning.
This article introduces ten fundamental software architecture patterns—layered, client‑server, master‑slave, pipe‑and‑filter, broker, P2P, event‑bus, MVC, blackboard, and interpreter—explaining their structures, typical applications, advantages, and drawbacks to help engineers choose the right architecture for large‑scale enterprise systems.
This article explains how to assess and design system capacity by analyzing real‑world scenarios—such as a company sports event—calculating required concurrency, average and peak QPS using the 80/20 rule, performing load tests, and determining instance counts to ensure reliable performance under varying traffic spikes.
This article explores the fundamentals of IT monitoring, examines common challenges such as scalability, reliability, and alert fatigue, compares four implementation approaches—from open‑source to fully custom solutions—and presents practical techniques like alert convergence, suppression, and automation to build a robust, adaptable monitoring platform.
This article presents typical examples of software architecture diagrams—including application, technical, security, and deployment views—to help developers understand and reference common architectural patterns in everyday project development.
This article explains how software architecture mirrors building construction, emphasizing the need for holistic design, systematic splitting, cognitive abstraction, visual modeling, and gradual evolution to build scalable, high‑performance, and maintainable distributed systems.
An extensive diagram presents a panoramic view of an enterprise technology middle‑platform architecture, illustrating its layered components, data flow, service governance, capability services, and integration points, offering a comprehensive visual guide for architects and engineers designing scalable internal platforms.
This article explains how to estimate and design system capacity—including traffic, concurrency, QPS, and resource requirements—by illustrating concepts, analytical formulas, peak‑load assessment techniques, performance testing, and a practical case study of a book‑reservation system.
This article analyzes the stability challenges of a multi‑store chain’s product‑copy mechanism, outlines design goals for isolation and scalability, and presents short‑ and long‑term monitoring, flow‑control, and emergency‑response strategies to ensure reliable large‑scale operations.
The article explains why scalability is crucial for software systems, outlines the difficulty of accurately predicting future changes, and presents two architectural approaches—layer separation and abstraction/implementation layers—illustrated with diagrams and design‑pattern examples to help architects manage complexity.
This article compiles detailed interview experiences, question lists, and practical advice for candidates targeting backend, big‑data, and cloud positions at leading Chinese tech firms, offering timelines, personal background, preparation tips, and reflections to help job seekers navigate multi‑round technical interviews efficiently.
This article explains the essence of software architecture, outlines its main components, classifies various architecture layers such as business, application, code, and technical architecture, discusses evolution stages, measurement criteria, common pitfalls, and provides a comprehensive knowledge framework for architects.
This article explains the evolution of software development from machine language to high‑level languages, describes the two software crises and the emergence of structured, object‑oriented, and component‑based design, and clarifies key architectural concepts such as systems, subsystems, modules, components, frameworks, and architecture itself.
This article traces the evolution from machine code to high‑level languages, explains the two software crises, defines system, subsystem, module, component and framework, and clarifies the true purpose and goals of software architecture for modern developers.
This article provides a comprehensive overview of database system design, covering the historical evolution, classification of relational and NoSQL databases, common architectures, consistency models, indexing techniques, storage formats, compression, and practical considerations for selecting and optimizing database solutions.
This article explains the fundamentals of software architecture diagrams, introduces the 4+1 view taxonomy and the C4 model, describes how to choose the right diagram for different audiences, and shares practical tips, common pitfalls, and tool recommendations for clear, self‑describing architecture visuals.
The article examines the historical evolution of software modularity, explains why microservices are an extreme reaction to monoliths, discusses isolation challenges across layers, and offers practical criteria for deciding where service boundaries should be drawn in modern backend systems.
By applying the DRY principle, the team abstracted audit requirements into a micro‑core plugin architecture, built a two‑week MVP for Xianyu’s community moderation, and demonstrated how systematic research, reusable patterns, and incremental evolution prevent duplicated effort and create a scalable, maintainable audit system.
This article explains the architecture, reliability mechanisms, dynamic configuration, monitoring, and alerting strategies of JD Daojia Open Platform's Business Message Queue (BMQ), illustrating how the system handles bidirectional communication, fault isolation, and scalable message processing for merchants.
This article introduces ten widely used software architectural patterns, explains their structure, typical usage scenarios, and lists their advantages and disadvantages, concluding with a comparative table that helps developers choose the most suitable architecture for their systems.
This article explores the evolution of software development from machine language to high‑level languages, explains the two software crises, and defines software architecture by distinguishing systems, subsystems, modules, components, and frameworks, emphasizing architecture as a top‑level structural solution for managing complexity.
This article explores what a web architect does, the core value they bring to software projects, and the extensive technical and soft‑skill competencies required, offering a practical roadmap for developers aspiring to transition from coding to strategic system design.
This article explains why architecture diagrams are essential for communication, defines key concepts, introduces the 4+1 view classification, outlines criteria for good diagrams, and presents the C4 modeling method with practical examples to help teams produce self‑describing, audience‑focused system visuals.
Learn a step‑by‑step methodology for drawing effective software architecture diagrams, covering the purpose of different diagram types, common pitfalls, audience‑focused design principles, and a detailed introduction to the C4 model with practical examples and visual guidelines.
This article explains the evolution of high‑availability strategies for stateful backend services, comparing cold backup, dual‑machine hot standby, same‑city active‑active, cross‑city active‑active and multi‑active solutions, and discusses their trade‑offs, implementation details, and practical considerations.
The article shares a senior developer’s firsthand observations on how architects differ in attitude, technical depth, system‑level responsibilities, and collaboration, offering practical steps and mindset changes needed to transition from senior engineering to a full‑stack architecture role.
This article provides a comprehensive overview of major software architecture approaches—including layered, multi‑tier, service‑oriented, and microservice architectures—explaining their motivations, structures, advantages, disadvantages, and when to apply each pattern in modern software development.
The article outlines a microservice‑based user‑center architecture for handling over one hundred million users, detailing gateway, core, and async services, interface design, vertical and horizontal database sharding, token graceful degradation, multi‑layer password security, event‑driven async processing, and comprehensive monitoring for high availability, performance, and security.
This article explains the purpose and types of software architecture diagrams, introduces the C4 modeling approach, highlights common pitfalls, and offers a step‑by‑step methodology to create clear, self‑describing diagrams that effectively communicate system structure to the right audience.
The paper presents an AB‑testing platform that structures experiments into scenes, buckets, layers and traffic, uses a salted‑hash based allocation and a two‑step “multi‑withdraw‑fill” algorithm to adjust percentages while preserving user‑experiment stability, and describes a lightweight, cache‑centric system architecture with staggered config reloads and safeguards against database spikes and zombie nodes.
This article explains the purpose and classification of software architecture diagrams, introduces the 4+1 and C4 modeling approaches, outlines criteria for good diagrams, addresses common pitfalls, and provides practical guidance and tool recommendations for producing clear, self‑describing architecture visuals.
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.
