This article explores the structure and development workflow of WeChat Mini Programs, detailing their view and logic layers, WXML/WXSS syntax, component system, routing, performance advantages, limitations, and how their concepts compare to Progressive Web Apps.
This article presents a comprehensive case study of a business monitoring system, covering its background, architectural analysis, module design, time‑series database selection, visualization with Grafana, alerting strategies, decision‑making logic, and intelligent monitoring experiments, followed by key takeaways and lessons learned.
Over three years, a small fintech company transformed its platform from a single‑server PHP/Java stack to a micro‑service‑based Spring Cloud architecture, undergoing four major upgrades that introduced distributed systems, SOA governance, big‑data pipelines, MongoDB replication, Redis caching, and open‑source tools, enabling transaction volumes exceeding one hundred billion.
This article details Alibaba's real‑time computing architecture for the 2016 Double 11 event, covering background, core components such as DRC, TT, Galaxy, OTS, XTool and OneService, and explains optimization techniques, fault‑tolerance strategies, stress‑testing practices, and future upgrade plans to handle massive streaming data workloads.
Meituan’s Xiamen frontend team created the app‑proto framework— a convention‑over‑configuration, self‑contained system that separates a Node data‑proxy/routing layer, a pure web interaction layer, and operational tooling—enabling mock‑first development, incremental technology adoption, modular replaceability, and automated CI/CD with Docker for fast, reliable merchant‑facing single‑page tools.
This article details how JD.com rebuilt its 2016 homepage using the Athena front‑end engineering suite, covering overall architecture, unified development workflow, performance and experience optimizations, reliability mechanisms, data‑driven monitoring, and future directions such as static pre‑loading and architectural upgrades.
This article details the architecture, chunked upload strategy, event handling, Redis caching, database sharding, and performance optimizations of a cloud‑based video surveillance storage system that evolved through versions 2.0, 3.0, and 4.0 to handle high‑concurrency alarm video uploads.
In this talk, Alibaba senior wireless expert Sun Bing details Xianyu's journey from a small startup to a massive P2P community, revealing the evolving technical architecture, key design principles, dynamic front‑end/back‑end integration, service‑bus implementation, and data‑driven strategies that powered its rapid growth.
This article explores how to build a high‑traffic insurance O2O platform for tens of millions of users by emphasizing simple micro‑service architecture, detailed functional requirements, performance targets, distributed storage, caching, service registration, and a practical technology stack for reliable, extensible backend development.
The article shares a detailed case study of constructing a high‑availability transaction platform for a major travel website, covering team organization, requirement analysis, architectural design, core modules such as search, order creation, and payment, as well as design principles, async processing, and post‑release reflections.
In this interview, Lianjia’s big‑data platform lead Lv Yi discusses his career, the motivations for joining Lianjia, the evolution of the company’s data infrastructure, architectural decisions, and the challenges of scaling a big‑data platform for real‑estate operations.
In this interview, Sogou architect Liu Jian shares how his team built a highly available, scalable commercial advertising platform, discusses the evolution of its infrastructure, offers practical advice for engineers aspiring to become architects, and reflects on emerging technologies and time‑management strategies.
This article details JD.com senior frontend architect Liu Wei's presentation on the challenges of a high‑traffic e‑commerce homepage and explains the static page generation pipeline, overall JS/CSS architecture, floor‑by‑floor loading strategy, disaster‑recovery measures, performance optimizations, and the JDF engineering toolchain that supports modular development and rapid deployment.
From its 2009 launch with a simple WAP site to handling over 100 million daily active users, Mobile Taobao’s architecture evolved through four stages—introducing API gateways, HTML5/WebApp integration, Bundle deployment, and the PackageApp system—while building comprehensive R&D, testing, operations, and release support.
The CAT real‑time monitoring system, open‑sourced in 2014 for Java applications, combines a lightweight ThreadLocal‑based client SDK, Netty‑driven asynchronous transport, and a highly scalable backend that processes ~100 TB of logs daily across 70 machines, using custom binary serialization, in‑memory modeling, segmented storage with 48‑bit indexing, and hourly aggregation to provide near‑full‑volume fault detection, localization, and performance analysis.
This article recounts Zhihu's evolution from a two‑person startup to a platform serving over 80 million monthly users, detailing early Python/Tornado choices, high‑availability, custom logging, event‑driven design, rendering optimizations, and the transition to a service‑oriented architecture.
This article reviews UML basics, corrects earlier mistakes, and explains how and when to apply sequence, component, and state diagrams—covering their elements, modeling rules, and practical examples—to help architects build clear abstract models.
This article outlines comprehensive e‑commerce platform architecture practices—including caching strategies, indexing, parallel and distributed computing, load balancing, sharding, high availability, monitoring, resource optimization, and messaging—to improve system performance, scalability, and reliability under high concurrency.
This article describes a scalable architecture for large Angular2 single‑page applications, covering communication layers, predictable state management with Redux/NgRx, modular design, lazy loading, dependency injection, and provides code examples illustrating models, components, and services for both single‑player and multiplayer scenarios.
This article presents a detailed case study of Vipshop's log platform during the 419 sales event, analyzing the 2013 architecture, bottlenecks in RabbitMQ and Storm, and the subsequent redesign using Kafka, Impala, and HBase to achieve scalable, reliable big‑data processing.
This article introduces Druid as an open‑source, distributed column‑store OLAP engine, explains its architecture and indexing mechanisms, discusses real‑time and batch data ingestion for order analytics at Qunar, compares it with other engines, and shares practical tips and pitfalls.
This article explains how to combine MVP architecture with RxJava in Android development, covering framework selection, step‑by‑step MVP construction, thread management using RxJava, and practical Q&A on testing, modularization, and memory‑leak prevention, providing a comprehensive guide for building decoupled, responsive mobile apps.
This talk traces the evolution of recommendation systems from early algorithm‑centric prototypes through a wild‑growth phase to a mature, architecture‑driven design, highlighting practical challenges, design principles, and lessons learned for building scalable, maintainable recommendation platforms.
This article provides a comprehensive overview of Apache Tomcat's modular architecture, detailing the roles and interactions of Connectors, Containers, Services, Servers, and the Lifecycle interface, while illustrating key implementation classes and code snippets that govern request handling and component management.
This article shares the experience of a Qunar hotel team refactoring their hotel homepage with React Native, detailing the initial native‑style approach, challenges with Redux, robustness and animation performance, and the subsequent architectural redesign that improved maintainability and user experience.
Distributed queue programming treats a queue as a fundamental, cross‑process abstraction, guiding developers to select synchronous or asynchronous, decoupled, persistent messaging solutions and offering four core models—point‑to‑point, producer‑consumer, publish‑subscribe, and MVC—while the article illustrates real‑world designs for billing, cache updates, and ticket processing.
The article provides a comprehensive overview of Twitter's Heron stream processing system, comparing its architecture, design principles, back‑pressure mechanisms, resource utilization, and performance test results with Storm/JStorm, and concludes with practical insights for large‑scale deployments.
This article explains how to choose an Android framework, build a layered MVP architecture, and use RxJava to move network requests off the main thread, providing clear code examples and practical tips for scalable, testable mobile apps.
The Meitu Technology Salon’s second offline session, held on July 24 2016, gathered senior R&D engineers to explore practical Golang applications through three case studies—Meitu’s high‑performance services, Panda TV’s live‑streaming architecture overhaul, and NetEase’s P2P cache system redesign—offering insights and networking for 100 participants.
This article presents a comprehensive overview of Qunar’s mobile hybrid solution—Hy—including its definition, advantages over native and web apps, architectural components such as Yo, QApp, Kami, Hytive, multi‑WebView strategy, offline update mechanism, development tools, challenges like CrossWalk integration, and future directions compared with QRN.
The article chronicles how 58.com’s website architecture evolved from a tiny, single‑machine setup to a distributed, service‑oriented platform by progressively addressing scaling challenges with LAMP, read/write separation, vertical business splitting, caching, cloud‑native services, and automation, illustrating the practical steps needed as traffic grows from tens of thousands to billions of requests.
The discussion explores various perspectives on front‑back end separation, covering definitions, benefits, architectural patterns, technology choices like Node.js, Vue, Angular, and practical considerations such as API design, performance, and deployment strategies.
This article details the technical background and evolution of the Duosuo English learning app, covering initial architecture, bandwidth estimation, risk control, database sharding, code refactoring, and operational lessons learned over four months of scaling.
The article details the evolution of Taobao's home page over the past year and a half, covering its background, the shift from a PHP‑based rendering system to a Node‑based platform, module construction, dynamic data integration, performance optimizations, stability measures, monitoring, and agile operational practices.
This article examines the analysis and optimization of a high‑traffic e‑commerce website, covering problems such as server waste and tight coupling, and presenting solutions including business splitting, application clustering, multi‑level caching, distributed sessions, and deployment diagrams to improve scalability and reliability.
This article explains the complex front‑end requirements of WeChat’s product‑editing feature accessed via the Scan function and details a modular, MMVC‑based architecture with real‑time preview, dynamic validation, and mapping techniques to simplify intricate attribute interactions.
This article examines the objectives, technical challenges, and evolutionary steps of large‑scale website architecture, covering resource separation, caching mechanisms, high‑availability techniques, CDN and distributed storage, as well as foundational design principles such as ACID/BASE and the CAP theorem.
This article chronicles Hotjar's evolution from a simple two‑server setup to a robust, eight‑server architecture handling billions of daily requests, sharing eight practical lessons on scaling, CDN usage, language choice, data storage, monitoring, and cost‑effective optimizations for fast‑growing web services.
After transitioning from JavaEE to Android development, the author shares practical insights on designing robust mobile app architecture, covering maintainability, extensibility, security, onboarding ease, documentation, packaging, and the trade‑offs between MVC and MVP, while offering guidance on framework selection and effective encapsulation.
This article shares practical insights on Android app architecture, covering maintainability, extensibility, security, onboarding friendliness, documentation, package organization, MVC vs MVP patterns, and guidelines for selecting and encapsulating frameworks to build robust mobile applications.
This article walks through the functional and non‑functional requirements of a B2C e‑commerce platform, illustrates a progression from a three‑server starter architecture to a clustered high‑availability design, and details capacity‑planning calculations for supporting millions of users and peak traffic spikes.
This article provides a comprehensive overview of HBase, covering its distributed architecture, component roles, data organization, read/write mechanisms, and best practices for schema and region design to ensure efficient big‑data storage and retrieval.
The article recounts a year‑and‑a‑half of evolving Taobao’s massive home page, detailing its shift from a PHP‑based rendering system to a Node‑powered architecture, the modular building platform, dynamic data integration, performance optimizations, stability measures, and agile deployment practices that keep billions of daily visits smooth.
This article details the step‑by‑step evolution of the English Fluency Android app’s architecture, covering its early broadcast‑based design, the adoption of a plugin‑based modular core, multi‑process integration, auxiliary systems such as asynchronous loading, event bus, monitoring, and support components for file storage, DNS protection, image loading, and downloading.
The article explains how to successfully launch and drive large‑scale architecture refactoring by translating technical jargon into plain language, using data‑driven arguments, empathizing with stakeholders, and employing structured escalation and win‑win negotiation tactics to align cross‑functional teams.
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.
Uber’s adoption of microservices showcases both the flexibility of using multiple languages and independent release cycles, while also exposing challenges such as duplicated effort across teams, type‑unsafe JSON interfaces, and the need for rigorous failure testing, offering valuable lessons for large‑scale system design.
This article details Medium’s evolution from its initial AWS‑based backend stack to a sophisticated, service‑oriented architecture that leverages Node.js, Go, DynamoDB, Redis, Aurora, Neo4j, Spark, and CI/CD pipelines to support millions of users.
This article traces the step‑by‑step evolution of large‑scale website architectures—from single‑server setups to distributed services—highlighting key techniques such as server clustering, caching, load balancing, database sharding, CDN usage, and the adoption of NoSQL and micro‑service frameworks.
This article outlines eBay's seven key scalability best practices—including functional partitioning, horizontal sharding, avoiding distributed transactions, asynchronous decoupling, stream processing, virtualization, and strategic caching—to illustrate how large‑scale web platforms can achieve linear resource growth and high availability.
The article explains how building low‑latency applications relies on simplicity, minimizing data transformations, using lightweight libraries, and separating business from infrastructure code to achieve high performance, maintainability, and reduced operational costs.
The 2016 ATF Alibaba Technology Forum presented a comprehensive overview of Alibaba's mobile e‑commerce platform, detailing massive scale challenges, user‑experience driven innovations, container‑based client architecture, the Weex framework, and future directions such as live video, VR/AR, and high‑performance mobile networking.
The article breaks down Twitter’s core business of following and being followed, explains its three‑tier presentation‑logic‑data architecture, details cache strategies, message‑queue isolation, and the push‑pull trade‑offs, illustrating how these components work together to achieve high‑performance, fault‑tolerant service at massive scale.
This article introduces OpenStack, the open‑source cloud operating system, explains its role compared to Linux, outlines its core services such as compute, storage, networking and identity, and describes the main projects and loosely‑coupled architecture that power modern IaaS platforms.
This article provides a comprehensive technical summary of large‑scale distributed website architecture, outlining characteristics, architectural goals, patterns, and detailed strategies for high performance, high availability, scalability, extensibility, security, and agility, supplemented with illustrative examples and practical insights.
The article examines why software architectures inevitably degrade over time in long‑running projects, analyzes the stages of decay, and presents practical strategies—including environment upgrades, phased and distributed builds, component isolation, and platform‑plus‑app designs—to keep systems maintainable and performant.
This article explains how the Flux data‑driven architecture, originally created for Facebook's web client, can be adapted for Android applications, describing its four core modules, their interactions, and a practical ToDoList example with code snippets.
This article introduces CAT, a Java‑based open‑source distributed real‑time monitoring system, covering its origins, design goals, architecture, message processing pipeline, instrumentation model, and how it achieves high availability, scalability, and low‑latency analytics for large‑scale internet services.
This article explains the purpose of architectural design in Android apps and provides a detailed comparison of MVC, MVP, and MVVM patterns, including their structures, advantages, drawbacks, code examples, as well as an introduction to AOP and practical development tips.
This article details the design and implementation of 58’s real‑time messaging platform, covering its business background, overall architecture, protocol design for extensibility and debugging, and solutions for fast TCP reconnection to ensure stable, high‑throughput delivery for intra‑city freight services.
The article outlines how Meipai’s rapidly growing platform built a backend system that guarantees high availability, handles massive traffic, supports evolving media formats, and adopts a multi‑language development model with clear principles for language selection and systematic integration.
The article details Stack Overflow’s 2016 infrastructure upgrades—including hardware, networking, load balancing, caching, database, and service layers—that enabled the site to process over 61 million daily requests while reducing processing time by hundreds of hours.
This article provides a comprehensive overview of Oracle Database architecture, detailing the server components, instance memory structures such as SGA, essential background processes, and the physical and logical storage layers, helping readers understand how Oracle organizes data and manages operations.
This article presents a comprehensive e‑commerce website architecture case study, detailing functional and non‑functional requirements, initial single‑server design, capacity estimation, and progressive evolution toward a distributed, high‑availability architecture with clustering, caching, load balancing, service‑orientation, and database sharding.
This article surveys the progression of game server architectures across eight types, detailing how early text‑based MUD servers evolved through multi‑threaded, distributed, and seamless‑world designs to modern hybrid action/MMO back‑ends, highlighting key technologies, scaling strategies, and architectural trade‑offs.
ZooKeeper is an open‑source distributed coordination service that provides high‑performance, reliable primitives such as naming, configuration management, leader election, locks and queues, and its internal design features a leader‑based server cluster, in‑memory hierarchical namespace, and transparent client routing for read/write operations.
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.
An in‑depth look at the rapidly growing IoT platform market reveals four platform types, an eight‑component architecture, diverse entry strategies, the pivotal role of open‑source interoperability, and how data and connectivity drive true platform value, backed by market forecasts and real‑world examples.
This article explains the benefits and drawbacks of performance optimization, distinguishes between single‑application and structural optimization approaches, outlines common steps, tools, and techniques for each, and presents case studies illustrating architectural evolution for improved scalability and stability.
Pinterest grew from zero to over 100 billion monthly page views by rapidly expanding its infrastructure, adopting simple, mature technologies like MySQL, Redis, and Memcache, and transitioning from clustering to sharding, offering practical lessons on scaling, tool selection, ID design, and migration strategies for massive growth.
This article explores the benefits and trade‑offs of performance optimization, outlines single‑application and structural optimization approaches, details bottleneck identification methods, common tuning techniques, and illustrates architectural evolution with diagrams to guide effective ops improvements.
This article outlines how a startup progressively upgraded its image‑centric product architecture on Alibaba Cloud—from rapid ECS/RDS deployment, through OSS + CDN acceleration, to caching with Memcache and horizontal scaling with SLB load balancing—offering practical guidance for similar teams.
The article chronicles Yirendai’s four‑stage backend evolution—detailing the bottlenecks, architectural redesigns, logging improvements, and service‑splitting strategies that transformed a single‑server system into a scalable, multi‑service platform.
This article reviews the most popular iOS architectural patterns—MVC, MVP, MVVM, and VIPER—explaining their responsibilities, testability, and maintainability, and provides concise code examples so developers can decide which pattern best fits their project requirements.
This article chronicles JD.com's POP platform evolution from a simple monolithic system in 2010 to a micro‑service‑based, highly scalable architecture by V3.0, highlighting the technical challenges, solutions, and the introduction of service‑oriented APIs, diversified data stores, and unified operational tools.
This article explains the fundamentals of microservice architecture, its key characteristics, componentization, business-aligned organization, decentralized governance, data management, infrastructure automation, fault‑tolerance design, and how these aspects intertwine with DevOps practices to enable faster, more flexible continuous delivery.
This article explains Apache Kafka’s core concepts, high‑throughput design choices such as sequential I/O, PageCache, Sendfile, and partitioning, and provides practical performance tips and configuration recommendations for brokers, producers, and consumers in large‑scale data pipelines.
This article provides a comprehensive overview of React Native, covering its motivation and design principles, the recent migration of Alibaba’s iPad “Guess You Like” feature, detailed planning for integration, and potential risks such as platform support, performance, and App Store policies.
The article outlines six major security design mistakes—compatibility, cost‑cutting, mixing data and code, closed designs, blacklist defenses, and neglecting security as a design goal—illustrating each with real‑world examples and offering practical recommendations to build more robust software and hardware architectures.
This article shares practical insights on rapidly creating a SaaS customer service platform, designing high‑availability architecture, and boosting overall system performance through load balancing, database replication, distributed caching, CDN acceleration, front‑end SPA frameworks, advanced search, and comprehensive monitoring.
An in‑depth interview with 1hao Store’s senior tech director reveals the evolution of its e‑commerce architecture, hybrid‑cloud strategy, performance‑driven culture, and practical steps for achieving high availability, elasticity, and cost efficiency during massive traffic spikes.
This article chronicles a developer's five‑year journey of designing a system by starting with the business layer, exploring entities, repositories, services, view models, MVC, and tooling, while highlighting common pitfalls and practical solutions for backend architecture.
This article details the overall architecture of an instant‑messaging client, covering protocol encapsulation, task flow, various timer implementations, state management, reconnection logic, login process, asynchronous handling, and local caching strategies for reliable communication.
This article recounts Zhihu's evolution from a tiny Python‑Tornado service on a single Linode to a massive, highly available backend employing custom logging, event‑driven processing, page‑render optimizations, and a service‑oriented architecture that now supports over 100 million users.
This article summarizes a WeChat group Q&A on the current momentum of in‑memory computing, compares TimesTen and SAP HANA, and offers practical advice on building enterprise big‑data platforms, covering cloud vs self‑build, talent, investment, and real‑world case studies.
This article details Baiba's evolution from a simple flash‑sale site to a mobile‑centric e‑commerce platform, describing its backend flow through CDN, caching layers, PHP‑FPM, memcached, Redis, MySQL, search engines, monitoring tools, deployment pipelines, and future plans for service‑orientation and hybrid apps.
This article provides a comprehensive analysis of Docker 1.2's architecture, detailing each module's function, the internal workflow of key commands, and how Docker's design enables lightweight, secure container virtualization for modern cloud‑native applications.
This article explains the technical differences between "Internet+" and industrial IoT, outlines the three‑tier architecture (device, cloud, monitoring), details middleware platforms YFIOs and YFCloud, and presents several practical deployment examples across agriculture, health, fisheries and wastewater treatment.
The article chronicles how 58.com’s web architecture evolved from a tiny, single‑machine setup to a multi‑layer, Java‑based, highly available service‑oriented platform, detailing the technical decisions, scaling challenges, and automation practices adopted at each traffic milestone.
The article chronicles how 58.com’s website architecture evolved through multiple growth stages—from a tiny single‑machine setup to a distributed, service‑oriented platform—by addressing scaling bottlenecks with technologies such as LAMP, read/write separation, vertical splitting, caching, and automated deployment.
This article explains how to choose and design persistence solutions for iOS apps, covering NSUserDefaults, Keychain, file storage, databases, isolation between persistence and business layers, multithreading, and the Virtual Record pattern implemented via DataCenter and CTPersistance.
This article chronicles the step‑by‑step evolution of Weibo's recommendation system architecture—from the early independent 1.0 stage through the layered 2.0 phase to the current platform‑centric 3.0 design—detailing the driving business and technical factors, architectural components, advantages, shortcomings, and key outcomes at each stage.
The article analyzes the inherent drawbacks of Redis Cluster—such as its decentralized P2P design, gossip overhead, upgrade difficulty, lack of hot‑cold data separation, client protocol challenges, and implementation limits—and proposes architectural enhancements like proxy, dashboard, and agent components to improve scalability, manageability, and performance.
This article provides an in‑depth examination of Apache Kafka’s origins, design goals, core concepts such as brokers, topics, partitions, producers and consumers, compares it with other message queues, explains its storage format, configuration options, delivery guarantees, and includes practical Java code examples for partitioning and consumption.
This article details JD.com's transition from static to dynamic, high‑performance product detail page architecture, describing the multi‑layer system design, data heterogeneity, caching strategies, scaling techniques, operational challenges, and the solutions implemented to meet rapid business demands during massive traffic events.
This article presents a practical IoT layered architecture model, contrasting the classic three‑tier view with a four‑tier structure (hardware, coordination, service, and application layers), explains the role of each layer, and advocates using hexagonal architecture for the service layer in the Lan platform.
This article shares Snowball's (Xueqiu) high‑availability architecture, performance optimizations, and scaling strategies—including hybrid cloud migration, service decomposition, in‑memory caching, and metric‑driven monitoring—implemented to handle massive traffic spikes and operational challenges during a volatile stock market period.
This article explains Nginx’s lightweight kernel and modular design, detailing how the core, basic, and third‑party modules are organized by structure and function, and describing the roles of handlers, filters, and proxies in processing HTTP requests and responses.
This article compiles recent high‑availability architecture discussions covering plugin‑based system design, simple kanban tools, independent scheduling services, challenges of managing 60‑billion‑row tables, and the trade‑offs between UUIDs and custom distributed ID generators, offering practical insights for backend engineers.
This article explains Google App Engine's core design philosophies—including reuse of Google technologies, statelessness, hard limits, Protocol Buffers for service heterogeneity, and distributed storage—then details its front‑end, Datastore, service group, language‑specific implementations, and a typical HTTP request flow.
