<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Architecture on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/architecture/</link><description>Recent content in Architecture on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 30 May 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Product Thinking (1): Architecture Design — From Monolith to Autonomous Agents</title><link>https://www.chenk.top/en/product-thinking/01-architecture/</link><pubDate>Sat, 30 May 2026 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/product-thinking/01-architecture/</guid><description>&lt;h2 id="the-shape-of-a-system" class="heading-anchor">The Shape of a System&lt;a href="#the-shape-of-a-system" class="heading-link" aria-label="Permalink to this section" title="Copy link to this section">#&lt;/a>
&lt;/h2>&lt;p>Every architecture is a frozen argument. It records what you believed about the problem at the time you committed the code. Looking back across four systems I built over eighteen months — a marketing content platform (~70k lines TypeScript), a zero-dependency skill routing engine, an autonomous research agent (~315k lines Python), and a multi-model coding orchestrator — I can trace how my architectural instincts shifted. Not always forward. Sometimes sideways. But there is a clear progression: from &amp;ldquo;keep it in one process&amp;rdquo; to &amp;ldquo;let the agents govern themselves.&amp;rdquo;&lt;/p></description></item><item><title>OpenClaw QuickStart (3): The Six Layers That Make the Agent Loop Work</title><link>https://www.chenk.top/en/openclaw-quickstart/03-architecture/</link><pubDate>Fri, 10 Apr 2026 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/openclaw-quickstart/03-architecture/</guid><description>&lt;p>You can use OpenClaw for months without reading this. But the first time you need to write a skill, debug a misrouted message, or figure out why the agent forgot something, you&amp;rsquo;ll want to know what each component does.&lt;/p>
&lt;p>&lt;figure class="article-figure">
 &lt;img src="https://blog-pic-ck.oss-cn-beijing.aliyuncs.com/posts/en/openclaw-quickstart/03-architecture/illustration_1.png" alt="OpenClaw QuickStart (3): The Six Layers That Make the Agent Loop Work — Chapter overview" loading="lazy" decoding="async" class="content-image">
 
&lt;/figure>
&lt;/p>
&lt;hr>
&lt;h2 id="the-six-layers" class="heading-anchor">The six layers&lt;a href="#the-six-layers" class="heading-link" aria-label="Permalink to this section" title="Copy link to this section">#&lt;/a>
&lt;/h2>&lt;p>&lt;figure class="article-figure">
 &lt;img src="https://blog-pic-ck.oss-cn-beijing.aliyuncs.com/posts/en/openclaw-quickstart/03-architecture/fig1_six_layers.png" alt="The six layers of an OpenClaw agent: Channels, Gateway, Router&amp;#43;Sessions&amp;#43;Pi Agent, Tools&amp;#43;Skills, Memory&amp;#43;ContextEngine, LLM provider" loading="lazy" decoding="async" class="content-image">
 
&lt;/figure>
&lt;/p></description></item><item><title>LLM Engineering (1): Architectures from Transformer to MoE</title><link>https://www.chenk.top/en/llm-engineering/01-architectures/</link><pubDate>Fri, 27 Mar 2026 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/llm-engineering/01-architectures/</guid><description>&lt;p>The 2017 Transformer block is still the silhouette of every production LLM in 2026, but almost every internal piece has been swapped, sparsified, or specialized. This series covers the modern stack end to end — architecture, training, inference, retrieval, evaluation, safety, deployment. Chapter 1 is about the block itself: what attention looks like in a 2026 model, how MoE breaks the param-FLOPs link, and where the non-attention alternatives (Mamba, RWKV) actually beat the Transformer.&lt;/p></description></item><item><title>LLM Workflows and Application Architecture: Enterprise Implementation Guide</title><link>https://www.chenk.top/en/standalone/llm-workflows-architecture/</link><pubDate>Thu, 31 Jul 2025 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/standalone/llm-workflows-architecture/</guid><description>&lt;p>Most LLM tutorials end where the interesting work begins. They show you how to call a chat completion endpoint, attach a vector store, and wrap the whole thing in a Streamlit demo. None of that is wrong, but none of it is what breaks at 3 a.m. when 10,000 users hit your service at once and every other answer is a hallucination.&lt;/p>
&lt;p>This article is about everything that comes after the demo. It is opinionated on purpose: production LLM systems are mostly plain distributed systems with one non-deterministic component bolted on, and most of the engineering effort goes into containing that non-determinism. We will work through seven dimensions — application architecture, workflow patterns, the RAG-vs-fine-tune decision, deployment topology, cost, observability, and enterprise integration — keeping each one short, concrete, and grounded in the levers that actually move the needle.&lt;/p></description></item><item><title>System Design (8): Case Studies — URL Shortener, Chat System, News Feed</title><link>https://www.chenk.top/en/system-design/08-case-studies/</link><pubDate>Sun, 27 Jul 2025 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/system-design/08-case-studies/</guid><description>&lt;p>The best way to learn system design is to practice it. Reading about individual components — caching, queues, load balancers — builds your vocabulary, but designing a complete system is where you learn to compose those components into something that actually works.&lt;/p>
&lt;p>This article walks through three classic system design problems end to end. Each follows the framework from the first article in this series: clarify requirements, estimate scale, design the architecture, deep dive into critical components, and identify bottlenecks.&lt;/p></description></item><item><title>System Design (6): Microservices vs Monoliths — The Honest Tradeoff</title><link>https://www.chenk.top/en/system-design/06-microservices-vs-monoliths/</link><pubDate>Tue, 22 Jul 2025 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/system-design/06-microservices-vs-monoliths/</guid><description>&lt;p>In 2020, the team behind Segment — a customer data platform processing billions of events per month — published a blog post titled &amp;ldquo;Goodbye Microservices.&amp;rdquo; They had decomposed their monolith into over 140 microservices, and the result was not the engineering utopia they expected. Instead, they spent most of their time fighting the complexity of the distributed system itself: service discovery failures, cascading timeouts, inconsistent deployment pipelines, and an explosion of inter-service communication bugs. They consolidated back to a monolith and reported dramatic improvements in developer productivity and system reliability.&lt;/p></description></item><item><title>Cloud Computing (1): Fundamentals and Architecture</title><link>https://www.chenk.top/en/cloud-computing/fundamentals/</link><pubDate>Wed, 01 Feb 2023 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/cloud-computing/fundamentals/</guid><description>&lt;p>&lt;figure class="article-figure">
 &lt;img src="https://blog-pic-ck.oss-cn-beijing.aliyuncs.com/posts/en/cloud-computing/fundamentals/illustration_1.png" alt="Cloud Computing (1): Fundamentals and Architecture — Chapter overview" loading="lazy" decoding="async" class="content-image">
 
&lt;/figure>
&lt;/p>
&lt;p>Every team building software in 2025 inherits the same buy-or-rent question their predecessors faced — only the answer has flipped. Twenty years ago you put hardware in a closet; today you describe the hardware in YAML and a global provider conjures it up in seconds, bills it by the second, and tears it down when you stop paying. Cloud computing is not just &amp;ldquo;someone else&amp;rsquo;s computer&amp;rdquo;. It is a programmable, metered, multi-tenant abstraction over compute, storage and networking that has fundamentally changed how businesses are built and how engineers spend their day.&lt;/p></description></item></channel></rss>