<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>工程实践 - 分类 - Simi Studio</title>
        <link>/categories/%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5/</link>
        <description>工程实践 - 分类 - Simi Studio</description>
        <generator>Hugo -- gohugo.io</generator><language>zh-CN</language><managingEditor>simi@simi.studio (Simi)</managingEditor>
            <webMaster>simi@simi.studio (Simi)</webMaster><lastBuildDate>Mon, 30 Mar 2026 10:00:00 &#43;0800</lastBuildDate><atom:link href="/categories/%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5/" rel="self" type="application/rss+xml" /><item>
    <title>Hono 最佳实践</title>
    <link>/posts/hono-best-practices/</link>
    <pubDate>Mon, 30 Mar 2026 10:00:00 &#43;0800</pubDate>
    <author>simi@simi.studio (Simi)</author>
    <guid>/posts/hono-best-practices/</guid>
    <description><![CDATA[<p><a href="https://hono.dev/docs/" target="_blank" rel="noopener noreffer ">Hono</a> 是一个小巧、简洁、极速的 Web 框架，基于 Web 标准构建。它可以在任何 JavaScript 运行时运行。</p>]]></description>
</item>
<item>
    <title>Docker Compose 最佳实践</title>
    <link>/posts/docker-compose-best-practices-v2/</link>
    <pubDate>Sat, 28 Mar 2026 10:00:00 &#43;0800</pubDate>
    <author>simi@simi.studio (Simi)</author>
    <guid>/posts/docker-compose-best-practices-v2/</guid>
    <description><![CDATA[<p><a href="https://docs.docker.com/compose/" target="_blank" rel="noopener noreffer ">Docker Compose</a> 最擅长的事情其实很明确：把一组容器怎么一起跑描述清楚，然后让开发环境、测试环境、临时环境尽量一致。</p>]]></description>
</item>
<item>
    <title>Docker 最佳实践</title>
    <link>/posts/docker-best-practices/</link>
    <pubDate>Sat, 28 Mar 2026 10:00:00 &#43;0800</pubDate>
    <author>simi@simi.studio (Simi)</author>
    <guid>/posts/docker-best-practices/</guid>
    <description><![CDATA[<p>当前使用版本为 <a href="https://docs.docker.com/engine/release-notes/29/" target="_blank" rel="noopener noreffer ">Docker 29.4</a>。Docker Desktop 是 macOS 推荐的安装方式。</p>]]></description>
</item>
<item>
    <title>Redis 最佳实践</title>
    <link>/posts/redis-best-practices/</link>
    <pubDate>Sat, 28 Mar 2026 10:00:00 &#43;0800</pubDate>
    <author>simi@simi.studio (Simi)</author>
    <guid>/posts/redis-best-practices/</guid>
    <description><![CDATA[<p>当前使用版本为 <a href="https://redis.io/docs/" target="_blank" rel="noopener noreffer ">Redis</a> 8.6.2。</p>]]></description>
</item>
<item>
    <title>PostgreSQL 最佳实践</title>
    <link>/posts/postgresql-best-practices/</link>
    <pubDate>Thu, 05 Mar 2026 10:00:00 &#43;0800</pubDate>
    <author>simi@simi.studio (Simi)</author>
    <guid>/posts/postgresql-best-practices/</guid>
    <description><![CDATA[<p>当前使用版本为 <a href="https://www.postgresql.org/docs/" target="_blank" rel="noopener noreffer ">PostgreSQL</a> 18.3。先走官方文档的查询、索引、分区和 JSONB。安装命令只是入口。</p>]]></description>
</item>
<item>
    <title>Flask 最佳实践</title>
    <link>/posts/flask-best-practices/</link>
    <pubDate>Wed, 25 Feb 2026 10:00:00 &#43;0800</pubDate>
    <author>simi@simi.studio (Simi)</author>
    <guid>/posts/flask-best-practices/</guid>
    <description><![CDATA[<p><a href="https://flask.palletsprojects.com/" target="_blank" rel="noopener noreffer ">Flask</a> 3.1.x 依然是 Python Web 开发中最灵活、最耐用的选择之一。它的优势不在于“功能越多越好”，而在于可以清晰地掌控应用边界、依赖注入、部署方式和演进路径。</p>
<p>但 Flask 的轻量也意味着一个现实问题：<strong>框架不会自动做出正确架构决策</strong>。同样一个 Flask 项目，既可以长期保持清晰、稳定、可测试，也可以在若干版本后演变成全局状态混乱、业务逻辑四处分散、请求处理难以维护的系统。</p>
<p>这里不讲入门示例，而是聚焦 <strong>Flask 3.1.x 在生产环境中的工程化最佳实践</strong>。</p>]]></description>
</item>
<item>
    <title>Redis 7 新特性</title>
    <link>/posts/redis-7-new-features/</link>
    <pubDate>Mon, 22 Dec 2025 09:38:00 &#43;0800</pubDate>
    <author>simi@simi.studio (Simi)</author>
    <guid>/posts/redis-7-new-features/</guid>
    <description><![CDATA[<blockquote>
<p><strong>注</strong>：<a href="https://redis.io/blog/redis-8-0-ga/" target="_blank" rel="noopener noreffer ">Redis 8.0</a> 已于 2025 年正式发布（GA），引入向量搜索原生支持等新特性。这里只写 Redis 7 的核心特性，Redis 8 升级另说。</p>
</blockquote>
<p><a href="https://redis.io/docs/" target="_blank" rel="noopener noreffer ">Redis</a> 7 不只是版本升级，它把搜索、JSON 支持、图数据库整合成一个统一平台。下面是关键变化和选型边界。</p>]]></description>
</item>
<item>
    <title>PostgreSQL 性能优化</title>
    <link>/posts/postgresql-performance-optimization/</link>
    <pubDate>Sat, 20 Dec 2025 21:13:00 &#43;0800</pubDate>
    <author>simi@simi.studio (Simi)</author>
    <guid>/posts/postgresql-performance-optimization/</guid>
    <description><![CDATA[<p>慢查询通常先暴露在计划上，而不是在 <code>postgresql.conf</code> 里。按 <a href="https://www.postgresql.org/docs/current/using-explain.html" target="_blank" rel="noopener noreffer ">PostgreSQL</a> 的路径：先跑 <code>EXPLAIN (ANALYZE, BUFFERS)</code>，看清 Seq Scan 还是 Index Scan，再决定索引、写法和配置。</p>
<p>缺索引、函数包住列、统计信息过期、autovacuum 跟不上、代价参数按机械盘默认——都会让同一条 SQL 走全表。先读计划，再动旋钮。</p>]]></description>
</item>
<item>
    <title>Prometheus &#43; Grafana 监控实战：让 LLM 服务可见</title>
    <link>/posts/prometheus-grafana-monitoring/</link>
    <pubDate>Fri, 19 Dec 2025 20:21:00 &#43;0800</pubDate>
    <author>simi@simi.studio (Simi)</author>
    <guid>/posts/prometheus-grafana-monitoring/</guid>
    <description><![CDATA[<p>LLM 服务挂了而没人知道，多半是只盯着 CPU。<a href="https://prometheus.io/docs/" target="_blank" rel="noopener noreffer ">Prometheus</a> + <a href="https://grafana.com/docs/" target="_blank" rel="noopener noreffer ">Grafana</a> 能看见请求，但默认的 node 面板看不见 token、TTFT，也看不见 <code>model</code> 标签把时序基数打爆。</p>
<p>下面按抓取 → 查询 → 规则 → 面板写。正文里的 <code>llm_*</code> 名字是<strong>示例指标名</strong>，不是 Prometheus 或某个网关的标准导出。接入前对照实际 <code>/metrics</code>。</p>]]></description>
</item>
<item>
    <title>Python 最佳实践</title>
    <link>/posts/python-best-practices/</link>
    <pubDate>Wed, 15 Oct 2025 10:00:00 &#43;0800</pubDate>
    <author>simi@simi.studio (Simi)</author>
    <guid>/posts/python-best-practices/</guid>
    <description><![CDATA[<p>生产 <a href="https://docs.python.org/3/" target="_blank" rel="noopener noreffer ">Python</a> 先锁解释器版本和 <code>pyproject.toml</code>，再谈异步和性能。类型、测试、依赖锁定是默认，不是加分项。没有对照实验就不写「更快」或「生产级」。</p>]]></description>
</item>
</channel>
</rss>
