ITFLY8 Architecture Home - focused on architecture knowledge sharing and exchange, covering project management and product design. Includes large-scale distributed website architecture (high performance, high availability, caching, message queues...), design patterns, architecture patterns, big data, project management (SCRUM, PMP, Prince2), product design, and more.
This article explains why traditional database connection pools rely on blocking I/O and connection pooling instead of leveraging IO multiplexing, covering JDBC limitations, protocol constraints, ecosystem factors, and the trade‑offs between performance and code complexity.
This article explains how WeChat Pay tackled inconsistent iOS and Android implementations by building a unified C++ cross‑platform framework, introducing UseCase‑based business flow, a routing mechanism, and improved network request handling, resulting in fewer bugs, faster development, and higher productivity.
This article details the evolution of the "到家" recommendation system across three major versions, describing the initial strategy‑factory prototype, the problems it faced, the vertical and horizontal splits introduced in V2.0, the dynamic pipeline configuration and service separation in V3.0, and the future outlook for finer‑grained personalization.
This article explains how to monitor microservice architectures, describes log, tracing, and metric monitoring, compares open‑source tracing tools, outlines fault‑tolerance strategies such as timeout, rate‑limiting, degradation, async buffering and circuit breaking, and details access‑security mechanisms including gateway authentication, service‑side auth, and OAuth2.0 token flows, while also introducing container technology and its role in microservice deployment.
This article explains how an API development platform can manage the full API lifecycle—design, development, testing, deployment, monitoring, and orchestration—by leveraging object‑driven modeling, automatic CRUD generation, rule processing, service composition, and source‑code export for microservice deployment.
The article explains that technical debt stems not from clumsy coding but from poor communication and inadequate domain modeling, leading to fragmented abstractions, excessive boolean flags, and ultimately software bankruptcy, and suggests collaborative, model‑driven practices to reduce it.
Uber transitioned from a monolithic codebase to a service‑oriented architecture, detailing goals like 99.99% reliability, core vs optional code separation, DISCO dispatch optimization, real‑time location tracking with Kafka, Hadoop, Spark, and the supporting infrastructure such as load balancers, web sockets, and security layers.
Traditional Linux I/O relies on read() and write() system calls that involve multiple CPU and DMA copies and context switches, while modern optimizations such as zero‑copy, multiplexing, and page cache techniques reduce copying overhead, and understanding buffered, mmap, and direct I/O reveals their impact on performance.
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 the six-stage methodology for designing databases—system requirements analysis, conceptual design, logical design, physical design, implementation, and execution/maintenance—detailing each phase’s purpose, techniques, and visual illustrations to guide developers through a structured, standards‑compliant design process.
