<?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>技术 on Reed&#39;s Blog</title>
    <link>https://reedlv.com/tags/%E6%8A%80%E6%9C%AF/</link>
    <description>Recent content in 技术 on Reed&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>zh-cn</language>
    <lastBuildDate>Wed, 01 Oct 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://reedlv.com/tags/%E6%8A%80%E6%9C%AF/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>全链路压测下的 3 高系统设计经验总结</title>
      <link>https://reedlv.com/posts/load-test-3high-design/</link>
      <pubDate>Wed, 01 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://reedlv.com/posts/load-test-3high-design/</guid>
      <description>疫情期间全链路压测摸底容量与瓶颈：3 高系统设计矩阵（高并发、高可用、高扩展性）——功夫在平时，底气在压测。</description>
    </item>
    <item>
      <title>MySQL RC 隔离级别下的 GAP 死锁分析</title>
      <link>https://reedlv.com/posts/mysql-rc-gap-deadlock/</link>
      <pubDate>Sat, 09 Aug 2025 00:00:00 +0000</pubDate>
      <guid>https://reedlv.com/posts/mysql-rc-gap-deadlock/</guid>
      <description>RC 隔离级别下通常认为 Gap Lock 会被关闭，为什么仍然出现 GAP 死锁？通过简化模型复现 DEL + INSERT 死锁，分析唯一键检查的 Next-Key Lock 成因与三种解法。</description>
    </item>
    <item>
      <title>业绩提成系统架构设计思考</title>
      <link>https://reedlv.com/posts/commission-system-architecture/</link>
      <pubDate>Thu, 19 Jan 2023 01:27:00 +0800</pubDate>
      <guid>https://reedlv.com/posts/commission-system-architecture/</guid>
      <description>面对方案种类多、场景需穷举、链路复杂、计算多样的提成系统，用三分法——分治、分离策略、分层设计——重构架构，零故障迁移 2000 家客户。</description>
    </item>
    <item>
      <title>无用的设计模式（上篇）</title>
      <link>https://reedlv.com/posts/design-patterns-part-1/</link>
      <pubDate>Mon, 10 Aug 2020 00:00:00 +0000</pubDate>
      <guid>https://reedlv.com/posts/design-patterns-part-1/</guid>
      <description>理论学习中人人都说重要，工作实践中却找不到用武之地——从诞生背景、本质认知、学习方法到面向对象设计原则，重新理解设计模式。</description>
    </item>
  </channel>
</rss>
