Tags
Writing, research, projects, and photos around “Reliability”.
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
Using a multi-layer execution service as an example, this article breaks down the multiple levels of locality across request identity, edge routing, execution resources, and backend caches, then presents reusable approaches to routing, invalidation, failover, and observability.
Short
13 min read
Part of the column “Technical Systems” · Chapter 7
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 with referral rewards and transaction systems, this article designs reusable, auditable marketing infrastructure across campaigns, audiences, entitlements, budgets, attribution, risk, experimentation, messaging, and measurement.
Case
16 min read
Starting from the observability problems of a small API service, this article distills the minimum implementation of request IDs, distributed Traces, service discovery, health monitoring, log queries, reliability, and infrastructure governance.
Case
15 min read
How candidate chains, failure classification, per-turn identity, and cost formulas make multi-source model routing controllable and auditable.
View projectA recoverable URL state machine and an incident workflow for separating submission, crawling, indexing, and algorithm context.
Case
3 min read
Part of the column “Search Engine Growth” · Chapter 4
A page contract for identity, crawl boundaries, rendering, migrations, and Core Web Vitals.
Case
3 min read
Part of the column “Search Engine Growth” · Chapter 3
A policy-only DeepSeek Harness plugin that builds ordered, explainable, auditable model candidate chains per task and advances along them within bounded failure rules.
View projectEvery role owns its own delivery, and everyone shares accountability for production outcomes. A quality loop depends on monitoring, fast containment, precise fixes, and retrospectives.
Short
2 min read