<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Backend on TinyChen's Blog</title><link>https://tinychen.com/tags/backend/</link><description>Recent content in Backend on TinyChen's Blog</description><generator>Hugo</generator><language>zh-cn</language><lastBuildDate>Thu, 23 Jul 2026 12:00:00 +0800</lastBuildDate><atom:link href="https://tinychen.com/tags/backend/index.xml" rel="self" type="application/rss+xml"/><item><title>Octans-媒体库后端结果契约与配置可视化</title><link>https://tinychen.com/20260430-octans-backend-result-config-viz/</link><pubDate>Thu, 30 Apr 2026 12:00:00 +0800</pubDate><guid>https://tinychen.com/20260430-octans-backend-result-config-viz/</guid><description>&lt;p&gt;本文主要介绍一类自托管媒体库（以 Octans 后端为例）在两件看似无关、实则都决定「长期可维护性」的决策上如何收口：一是&lt;strong&gt;内部结果模型与错误契约统一&lt;/strong&gt;，二是&lt;strong&gt;配置可视化首版的边界&lt;/strong&gt;。前者解决 Controller / Service 各造一套 &lt;code&gt;*ServiceResult&lt;/code&gt; 的分裂；后者解决「配置能改、能看、能审计」与「部署覆盖、启动链路、权限面」之间的张力。讨论的是可被 supersede 的工程边界，不是某一版本的接口字段全集。&lt;/p&gt;</description></item></channel></rss>