<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>技术决策 on PlumePHP</title><link>https://plumephp.com/tags/%E6%8A%80%E6%9C%AF%E5%86%B3%E7%AD%96/</link><description>Recent content in 技术决策 on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Wed, 04 Nov 2026 08:40:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/%E6%8A%80%E6%9C%AF%E5%86%B3%E7%AD%96/index.xml" rel="self" type="application/rss+xml"/><item><title>《游戏服务端架构·平台化与架构治理》13.3 结语：架构是取舍，不是清单</title><link>https://plumephp.com/gs-arch-gov-13-3-conclusion-tradeoffs-not-checklist/</link><pubDate>Wed, 04 Nov 2026 08:40:00 +0800</pubDate><guid>https://plumephp.com/gs-arch-gov-13-3-conclusion-tradeoffs-not-checklist/</guid><description>全书结语：没有最好的架构，只有在给定约束下可解释的取舍。文章拆解把清单当架构、把平台当目的、把规模当唯一目标三类常见错误，给出取舍记录的结构、硬约束与软约束的区分和决策复盘方法，并说明第一次架构评审、第一张容量表和第一条 SLO 怎么落地。</description></item></channel></rss>