Tags
Writing, research, projects, and photos around “Architecture”.
Using multi-backend model access as the setting, this article explains how an AI Gateway handles resource scheduling, capacity control, failure switching, distributed state, usage accounting, and enterprise cost governance.
Short
16 min read
Part of the column “Technical Systems” · Chapter 9
Content, search, commerce, and growth systems repeatedly face the same challenge across multiple countries, industries, and scenarios: how to reuse stable capabilities while keeping business expressions distinct. How should boundaries be drawn between configuration, protocols, components, and orchestration?
Short
12 min read
Part of the column “Technical Systems” · Chapter 8
Starting from the fault structure of a multi-node execution system, this article reviews how requests, state, storage, performance, and failures gradually cross boundaries, and discusses how the next architecture should be reorganized.
Short
19 min read
Part of the column “Technical Systems” · Chapter 6
Starting from the different questions asked by analysis, operations, and engineering, this article organizes how a data center for a multi-source business platform should divide Tabs, define metrics, structure read and write paths, and handle billing, reconciliation, growth, and cost.
Short
22 min read
Starting from a multi-system integration experience, this essay distinguishes creation, task efficiency, organizational productivity, and business value—and asks where value and cost actually come from when AI enters a complex system.
Short
5 min read
Part of the column “Engineering & AI Judgment” · Chapter 10
A verifiable content model for structured data, images, video, and related-page context.
Case
2 min read
Part of the column “Search Engine Growth” · Chapter 6
This paper examines task decomposition, subtask capability classification, model selection, and bounded execution-time fallback, while reducing the broader Agent scheduling problem to an engineering slice of dsh-quota-router.
13 min read
Read summaryA multi-region system can neither cram every difference into a single core nor rebuild everything for each region. The key is to identify stable boundaries, preserve extension points, and clarify module ownership.
Short
3 min read
Part of the column “Technical Systems” · Chapter 4
Code decay rarely comes from any single moment of bad writing; it comes from local changes repeatedly bypassing shared boundaries. What truly needs maintaining is the consistency between design and collaboration.
Short
2 min read
Part of the column “Technical Systems” · Chapter 2