This article explains the six key types of architecture—business, product, application, data, technical, and project—detailing their core components, purposes, and examples, and shows how they interrelate to form a complete system design framework for organizations.
This comprehensive manual outlines ByteDance's Agent platform, covering its technical foundations, architecture, development workflow, real‑world application scenarios, operational optimization, security compliance, future innovation paths, case studies, team collaboration, risk mitigation, tooling, and global adaptation.
This article explains the definitions, core components, purposes, and real‑world examples of six architecture layers—business, product, application, data, technical, and project—and shows how they interrelate to form a complete system design framework.
This article explains the definition of technical architecture, outlines its core components such as technical services, components, infrastructure and selection, and illustrates how it supports business, application, and data architectures through layered system diagrams and practical examples.
The article explores the concept of “endgame thinking,” illustrating how starting from the desired future outcome and working backwards can improve product decisions, team management, technical architecture, and long‑term strategy, while warning against short‑sighted tactics, over‑design, and neglecting real constraints.
This article defines technical architecture and outlines its design steps, using a series of illustrative diagrams to guide readers through the core concepts and practical workflow of building robust system structures.
This article explains the essential role of technical architects, outlines common collaboration pitfalls, introduces a triangle cooperation model, and presents a step‑by‑step architecture thinking framework—including 0→1, 1→0, 1→2, 1→N, and decoupling techniques—to help teams build resilient, future‑proof systems.
This article explores the essential role of technical architects, detailing their responsibilities, the challenges of traditional waterfall collaboration, and introducing a triangular collaboration model and a structured architecture design thinking framework to foster system thinking, proactive decision‑making, and effective team leadership.
This article explains the pivotal role of technical architects in bridging business analysis, project execution, and architecture governance, introduces a triangular collaboration model to overcome information asymmetry, and presents a systematic 0→1→N thinking framework with practical methods for identifying key issues, decomposing complexity, and designing future‑proof, decoupled systems.
This comprehensive guide explains the purpose of architecture diagrams, the criteria for good diagrams, the optimal moments to create them, and detailed methods for drawing business, application, technical, code, and data architecture diagrams, complete with design principles, classification, and practical tips.
The article examines the myth that programmers must stop coding after age 35, explains why most continue to code, and outlines five viable career trajectories—including becoming a technical expert, moving into management, architecture, solution engineering, or product management—to maintain competitiveness and professional growth.
The article outlines a data‑space architecture that employs a wide‑table design with dynamic columns and dedicated metadata tables, a metadata execution engine for business‑logic mapping, upgraded SQL parsing via Druid, MySQL‑proxy protocol handling, and distributed flow control using Redis and Zookeeper to enable scalable, multi‑tenant, low‑code and cloud‑native data management.
This article details the technical design, challenges, and results of Taobao’s “Home‑Page as Venue” initiative, explaining how a new A/B‑page architecture replaced crowded promotional cards with a dynamic cat‑head entry, improved information‑flow efficiency, reduced development cost, and delivered measurable gains in traffic, conversion, and revenue during major sales events.
Electron enables developers to build cross‑platform desktop applications using web technologies by combining Chromium for UI rendering, Node.js for system APIs, and native modules, offering rapid delivery despite lower performance than native or Qt, while addressing challenges such as hardware‑acceleration glitches and XSS risks through configuration and governance.
This article explains the essential concepts of software architecture, distinguishing systems, subsystems, modules, components, frameworks, and architecture itself, and then details the various architectural layers—including business, application, data, code, technical, and deployment—while highlighting their purposes and design considerations.
This article explains the fundamental concepts of software architecture, distinguishing systems, subsystems, modules, components, and frameworks, and then details the various layers—business, application, data, code, technical, and deployment—while outlining the architect’s responsibilities and the criteria for when architecture design is needed.
This article compiles essential software architecture diagrams—including application, technical, security, and deployment views—providing visual references for developers to understand system structures, and encourages exploration of best practices in system design.
The article explains the concept of technical architecture, its role in defining reusable standards and guidelines, and outlines how to initiate enterprise technical architecture work by modeling future and current states, analyzing gaps, and organizing technical domains, patterns, and services for end‑to‑end solutions.
This article explains the fundamental concepts of software architecture, distinguishing it from frameworks, defining system, subsystem, module, and component, outlining the four core aspects of architecture, and detailing the various layers such as business, application, data, code, technical, and deployment architectures.
This article chronicles the evolution of Taobao’s shopping cart over four years, detailing its core functions, product positioning, business goals, user‑experience upgrades, technical breakthroughs, and future roadmap, while highlighting how strategic product and engineering improvements drove higher conversion and smoother checkout.
This article shares practical, structured thinking methods—ranging from user‑centric fact restoration to causal analysis and decoupling techniques—that help technical architects and leaders quickly clarify problems, build consensus, and design scalable, forward‑looking solutions while avoiding common pitfalls.
The article traces Taobao’s shopping cart evolution from a basic product‑management tool to a real‑time, AI‑enhanced platform, detailing business goals for user experience and conversion, four staged upgrades—including bundling, discount filtering, and seamless checkout—plus technical solutions such as Bloom filters, asynchronous pipelines, and nextRpc, while outlining operational expansions and future AI‑driven improvements.
This article explains how technical architecture transforms product requirements into concrete systems, tackles uncertainty in technology choices, and presents strategic principles—fit, simplicity, evolution—alongside tactical guidelines for high concurrency, high availability, and business design, supported by logical and physical diagram examples.
This article explores layered thinking in architecture design, detailing decomposition and integration, cloud three‑layer models, SOA component‑service‑process layering, and how to combine these approaches into coherent technical and application architectures for balanced business‑technology solutions.
This article explains the fundamental concepts of software architecture, distinguishing system, subsystem, module, component, framework and architecture, and details various architectural layers such as business, application, data, code, technical, and deployment architectures, highlighting their purposes and relationships.
This article explains how to design robust backend technical architectures by addressing strategic principles such as suitability, simplicity, and evolution, and tactical guidelines covering high concurrency, high availability, and business design, while illustrating logical and physical architecture diagrams and practical implementation tips.
This article clarifies the essence of software architecture by defining key concepts such as system, subsystem, module, component, framework versus architecture, and then details the multiple architectural layers—including business, application, data, code, technical, and deployment—while highlighting their purposes, relationships, and design considerations.
This article clarifies the fundamental concept of software architecture, distinguishes related terms such as system, subsystem, module, component, framework, and architecture, and outlines the five major architectural layers—business, application, data, code, technical, and deployment—providing a comprehensive guide for architects and developers.
This article outlines essential strategic and tactical principles for technical architecture, addressing uncertainty in technology choices, and detailing the suitability, simplicity, and evolution principles, as well as high‑concurrency, high‑availability, and business design guidelines to build stable, scalable systems.
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 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 document presents VM-Mapping, a solution for cross-scene data synchronization in mobile apps, addressing fragmented business scenarios and inconsistent UI states through annotation-based object mapping and data-driven UI updates.
This article explains how layered thinking and layered models guide architecture design, covering decomposition and integration, cloud three‑tier (IaaS‑PaaS‑SaaS) and SOA layering, the role of service and data layers, and how to combine cloud and SOA concepts into coherent architectural diagrams.
This article explains the concept of layered architecture thinking, covering decomposition and integration, cloud three‑tier models, SOA layering, application‑level three‑tier patterns, and how to combine cloud and SOA approaches into a coherent, multi‑view architectural blueprint.
This article explains the concept of technical architecture and enterprise technology architecture, covering reusable standards, future‑state modeling, technical domains, patterns, services, and an example of a multi‑tier transaction pattern, while also providing community resources for further learning.
This article examines Yanxuan's offline retail development, detailing its business models, technical architecture, price‑and‑marketing synchronization, product caching, precise replenishment, inventory integration, and O2O experiments, while outlining future growth prospects for omnichannel retail.
This article explains how layered thinking guides architecture design, covering cloud three‑tier (IaaS‑PaaS‑SaaS) and SOA three‑tier models, the role of decomposition and integration, and practical layering patterns for technical, application, and functional architectures across various domains.
Alibaba’s FaaS platform for Youku content distribution replaces traditional Java services with a gateway‑driven, containerized function runtime and one‑stop development/ops portal, delivering low‑cost development, isolated JVM execution, transparent monitoring, and rapid API and data‑source integration, dramatically speeding iteration while addressing classloader and lifecycle challenges.
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.
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.
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.
The article explains that a true technical middle platform is not just a set of tools or cloud‑native services but a business‑focused, organization‑wide foundation, and outlines six construction pillars—container cloud virtualization, comprehensive microservice framework, abstracted technical components, shared basic services, value‑driven DevOps/AIOps, and a dedicated efficiency team—to enable rapid change, innovation, and operational excellence.
The article examines why software projects often suffer from the paradox of many team members, few deliverables, and heavy workloads, identifying issues such as misaligned roles, poor code quality, communication overhead, mistrust, unclear requirements, and outdated architecture that collectively drain efficiency.
From 2011 to 2014 Ctrip shifted from a 25% online, 75% offline model to a mobile‑centric approach, reorganizing its 16 business units, decoupling systems, and adopting new engineering practices to improve performance, scalability, and team autonomy.
