deploy: bc22b4eaeb6005d9af7f32e09dbb1829a24ceddf

2 files changed, 303 insertions, 0 deletions

diff --git a/2025/03/17/二〇二五年三月十七日/index.html b/2025/03/17/二〇二五年三月十七日/index.html
index f14dfba7..359e440b 100644
--- a/2025/03/17/二〇二五年三月十七日/index.html
+++ b/2025/03/17/二〇二五年三月十七日/index.html
@@ -292,6 +292,11 @@ mjx-container[display="true"] + br {
     <nav class="post-nav">
         <div class="prev-item">
            
+                <div class="icon arrow-left"></div>
+                <div class="post-link">
+                    <a href="/2025/03/19/%E9%A2%86%E5%9F%9F%E9%A9%B1%E5%8A%A8%E8%AE%BE%E8%AE%A1%E4%B8%AD%E8%81%9A%E5%90%88%E6%A0%B9%E6%8C%81%E4%B9%85%E5%8C%96%E5%92%8C%E4%BA%8B%E4%BB%B6%E5%8F%91%E5%B8%83%E5%8F%AF%E8%83%BD%E5%AF%BC%E8%87%B4%E6%95%B0%E6%8D%AE%E4%B8%8D%E4%B8%80%E8%87%B4%E9%97%AE%E9%A2%98/">Prev</a>
+                </div>
+            
         </div>
         <div class="next-item">
             
diff --git a/2025/03/19/领域驱动设计中聚合根持久化和事件发布可能导致数据不一致问题/index.html b/2025/03/19/领域驱动设计中聚合根持久化和事件发布可能导致数据不一致问题/index.html
new file mode 100644
index 00000000..a45f739c
--- /dev/null
+++ b/2025/03/19/领域驱动设计中聚合根持久化和事件发布可能导致数据不一致问题/index.html
@@ -0,0 +1,298 @@
+<!DOCTYPE html>
+<html lang="en">
+  <head>
+    <meta charset="UTF-8">
+<meta name="viewport"
+      content="width=device-width, initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0">
+<meta http-equiv="X-UA-Compatible" content="ie=edge">
+
+    <meta name="author" content="韩暮秋">
+
+
+    <meta name="subtitle" content="暮秋小屋">
+
+
+    <meta name="description" content="这里是暮秋小屋，思念和灵感的寄存处">
+
+
+    <meta name="keywords" content="韩暮秋,MuqiuHan,'Muqiu Han', 'muqiu han', muqiuhan">
+
+
+
+
+<title>领域驱动设计中聚合根持久化和事件发布可能导致数据不一致问题 | 暮秋小屋</title>
+
+
+
+    <link rel="icon" href="/favicon.ico">
+
+
+
+<style>
+    @import url('https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700&family=Noto+Sans+SC:wght@300;400;500;700&family=Roboto+Mono&display=swap');
+</style>
+
+
+
+    <!-- stylesheets list from _config.yml -->
+    
+    <link rel="stylesheet" href="/css/style.css">
+    
+
+
+
+
+    <!-- scripts list from _config.yml -->
+    
+    <script src="/js/frame.js"></script>
+    
+
+
+
+
+    <script src="https://polyfill.io/v3/polyfill.min.js?features=es6"></script>
+    <script id="MathJax-script" async src="https://cdn.jsdelivr.net/npm/mathjax@3/es5/tex-mml-chtml.js"></script>
+
+
+
+
+
+
+
+  <meta name="generator" content="Hexo 6.3.0"></head>
+  <body>
+    <div class="mask-border">
+    </div>
+
+    <div class="wrapper">
+
+      <div class="header">
+  <div class="flex-container">
+    <div class="header-inner">
+      <div class="site-brand-container">
+        <a href="/">
+          
+            暮秋小屋
+          
+        </a>
+      </div>
+      <div id="menu-btn" class="menu-btn" onclick="toggleMenu()">
+        Menu
+      </div>
+      <nav class="site-nav">
+        <ul class="menu-list">
+          
+            
+              <li class="menu-item">
+                <a href="/">主页</a>
+              </li> 
+                   
+          
+            
+              <li class="menu-item">
+                <a href="/categories/gallery/">日记本</a>
+              </li> 
+                   
+          
+            
+              <li class="menu-item">
+                <a href="/tags/Medicine/">医学</a>
+              </li> 
+                   
+          
+            
+              <li class="menu-item">
+                <a href="/tags/Technique/">计算机科学</a>
+              </li> 
+                   
+          
+            
+              <li class="menu-item">
+                <a href="/tags/Life/">生活</a>
+              </li> 
+                   
+          
+            
+              <li class="menu-item">
+                <a href="/about">关于</a>
+              </li> 
+                   
+          
+          
+            <li class="menu-item search-btn">
+              <a href="#">Search</a>
+            </li>
+          
+        </ul>
+      </nav>
+    </div>
+  </div>
+</div>
+
+
+      <div class="main">
+        <div class="flex-container">
+          <article id="post">
+
+  
+    <div class="post-head">
+    <div class="post-info">
+        <div class="tag-list">
+            
+                
+                    <span class="post-tag">
+                        <a href="/tags/Techinique/">
+                            Techinique
+                        </a>
+                    </span>    
+                           
+            
+        </div>
+        <div class="post-title">
+            
+            
+                领域驱动设计中聚合根持久化和事件发布可能导致数据不一致问题
+            
+            
+        </div>
+        <span class="post-date">
+            Mar 19, 2025
+        </span>
+    </div>
+    <div class="post-img">
+        
+            <div class="h-line-primary"></div>
+              
+    </div>
+</div>
+    <div class="post-content">
+    <p>使用领域事件的一种直接做法是：在 <strong>应用服务</strong> (Application Service) 中产生事件并发布出去。例如，对于“用户昵称更新”的场景来讲，对应的应用服务 <code>UserCommandService</code> 实现如下：</p>
+<figure class="highlight fsharp"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">member</span> <span class="keyword">public</span> this.UpdateMyName (command<span class="operator">:</span> UpdateUsernameCommand) (user<span class="operator">:</span> User) <span class="operator">=</span></span><br><span class="line">  <span class="keyword">let</span> user <span class="operator">=</span> userRepository.GetById user.Id</span><br><span class="line">  <span class="keyword">let</span> oldName <span class="operator">=</span> user.Username</span><br><span class="line">  <span class="keyword">let</span> newName <span class="operator">=</span> command.Username</span><br><span class="line"></span><br><span class="line">  user.UpdateUsername newName</span><br><span class="line">  <span class="operator">|&gt;</span> userRepository.Save</span><br><span class="line">  </span><br><span class="line">  UsernameChangeEvent (user.Id, newName, oldName) </span><br><span class="line">  <span class="operator">|&gt;</span> eventPublisher.Publish</span><br></pre></td></tr></table></figure>
+
+<p>这里，在更新了用户姓名之后，即刻调用事件发布器 <code>eventPublisher.Publish</code> 将事件发送到消息队列中。虽然这种方式比较流行，但它至少存在两个问题：</p>
+<ol>
+<li>领域事件本应属于领域模型的一部分，也即应该从领域模型中产生，而这里却在应用服务中产生</li>
+<li>对聚合根（本例中的 <code>User</code> ）的持久化和对事件的发布可能导致数据不一致问题。</li>
+</ol>
+<p>对于第1个问题，可以采用“从领域模型中返回领域事件”的方式：</p>
+<figure class="highlight fsharp"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">member</span> <span class="keyword">public</span> this.UpdateMyName (command<span class="operator">:</span> UpdateUsernameCommand) (user<span class="operator">:</span> User) <span class="operator">=</span></span><br><span class="line">  <span class="keyword">let</span> user <span class="operator">=</span> userRepository.GetById user.Id</span><br><span class="line">  <span class="keyword">let</span> oldName <span class="operator">=</span> user.Username</span><br><span class="line">  <span class="keyword">let</span> newName <span class="operator">=</span> command.Username</span><br><span class="line"></span><br><span class="line">  user.UpdateUsername newName <span class="comment">// UpdateUsername 中构建 UsernameChangeEvent</span></span><br><span class="line">  <span class="operator">|&gt;</span> <span class="keyword">fun</span> user event <span class="operator">-&gt;</span> </span><br><span class="line">       userRepository.Save user</span><br><span class="line">       eventPublisher.Publish event</span><br></pre></td></tr></table></figure>
+
+<p>这种方式保证了领域事件是从领域模型中产生，但仍然存在第二个问题。</p>
+<p>第二个问题中所谓的“数据一致性”，表示的是将聚合根保存到数据库和将领域事件发布到消息队列之间的一致性。由于数据库和消息队列属于异构的数据源，要保证他们之间的数据一致性需要引入分布式事务。</p>
+<p>但是分布式事务通常是比较重量级的，再加上当下的诸多常见消息队列均不支持分布式事务（比如Kafka），因此并不建议使用分布式事务来解决这个问题。</p>
+<p><a target="_blank" rel="noopener" href="https://microservices.io/patterns/data/transactional-outbox.html">Transactional Outbox</a> 便是一种方案，概括来说，这种方式将一个分布式事务的问题拆解为多个本地事务，并采用“至少一次投递（At Least Once Delivery）”原则保证消息的发布。具体来讲，发布方在与业务数据相同的数据库中为领域事件创建相应的事件发布表（Outbox table），然后在保存业务数据的同时将所产生的事件保存到事件发布表中，由于此时二者都属于同一个数据库的本地事务所管辖，因此保证了“业务操作”与“事件产生”之间的一致性。此时的代码变成了：</p>
+<figure class="highlight fsharp"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">member</span> <span class="keyword">public</span> this.UpdateMyName (command<span class="operator">:</span> UpdateUsernameCommand) (user<span class="operator">:</span> User) <span class="operator">=</span></span><br><span class="line">  <span class="keyword">let</span> user <span class="operator">=</span> userRepository.GetById user.Id</span><br><span class="line">  <span class="keyword">let</span> oldName <span class="operator">=</span> user.Username</span><br><span class="line">  <span class="keyword">let</span> newName <span class="operator">=</span> command.Username</span><br><span class="line"></span><br><span class="line">  user.UpdateUsername newName <span class="comment">// UpdateUsername 中构建 UsernameChangeEvent</span></span><br><span class="line">  <span class="operator">|&gt;</span> <span class="keyword">fun</span> user event <span class="operator">-&gt;</span> </span><br><span class="line">       userRepository.Save user</span><br><span class="line">       eventStore.Save event <span class="comment">// 这儿用 eventStore 代替 eventPublisher 啦</span></span><br></pre></td></tr></table></figure>
+
+<p>应用服务不再将事件直接发布出去，而是将事件保存到数据库中，之后，另一个模块将从数据库中读取事件并发布。</p>
+<p>然而，这种方式依然有个缺点：每个需要产生领域事件的场景都需要应用服务先后调用<code>repository.Save()</code>和<code>eventStore.Save()</code>，导致了代码重复。解决方法也很简单——在聚合根中临时保存领域事件，然后在资源库中同时保存聚合根和领域事件到数据库。</p>
+<p>在这种方式下，首先需要在聚合根的基类中完成与领域事件相关的各种设施，包括创建临时性的事件容器<code>events</code>以及通用的事件产生方法<code>RaiseEvent()</code>：</p>
+<figure class="highlight fsharp"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line"><span class="meta">[&lt;AbstractClass&gt;]</span></span><br><span class="line"><span class="keyword">type</span> <span class="title class_">IAggregateRoot</span> <span class="operator">=</span> </span><br><span class="line">  <span class="operator">...</span></span><br><span class="line">  <span class="keyword">let</span> events <span class="operator">=</span> Collections.Generic.List<span class="operator">&lt;</span>DomainEvent<span class="operator">&gt;</span> ()</span><br><span class="line"></span><br><span class="line">  <span class="keyword">member</span> <span class="keyword">private</span> this.RaiseEvent (event<span class="operator">:</span> DomainEvent) <span class="operator">=</span></span><br><span class="line">    events.Add event</span><br><span class="line">  </span><br><span class="line">  <span class="operator">...</span></span><br></pre></td></tr></table></figure>
+
+<p>在聚合根基类<code>AggregateRoot</code>中，<code>events</code>字段用于临时保存聚合根中所产生的所有事件，各实际的聚合根类通过调用<code>RaiseEvent()</code>向<code>events</code>中添加事件。比如，对于“用户修改昵称”而言，<code>User</code>实现如下：</p>
+<figure class="highlight fsharp"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">member</span> <span class="keyword">public</span> this.UpdateUsername (name<span class="operator">:</span> <span class="type">string</span>, user<span class="operator">:</span> User) <span class="operator">=</span></span><br><span class="line">  <span class="keyword">if</span> this.Username <span class="operator">=</span> name <span class="keyword">then</span></span><br><span class="line">    ()</span><br><span class="line">  <span class="keyword">else</span></span><br><span class="line">    <span class="keyword">let</span> oldName <span class="operator">=</span> this.Username</span><br><span class="line">    this.Username <span class="operator">&lt;-</span> name</span><br><span class="line">    UsernameChangeEvent (user.Id, name, oldName) </span><br><span class="line">    <span class="operator">|&gt;</span> this.RaiseEvent</span><br></pre></td></tr></table></figure>
+
+<p>这里，聚合根 <code>User</code> 不再返回领域事件，而是将领域事件通过<code>AggregateRoot.RaiseEvent()</code>暂时性地保存到自身的<code>events</code>中。之后在保存<code>User</code>时，资源库的公共基类<code>BaseRepository</code>的<code>Save()</code>方法同时完成对聚合根和领域事件的持久化：</p>
+<figure class="highlight fsharp"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">member</span> <span class="keyword">public</span> this.Save<span class="operator">&lt;</span>AR<span class="operator">:</span> <span class="keyword">when</span> AR <span class="operator">:&gt;</span> AggrateRoot<span class="operator">&gt;</span> (it<span class="operator">:</span> AR) <span class="operator">=</span></span><br><span class="line">  <span class="keyword">match</span> it <span class="keyword">with</span></span><br><span class="line">  <span class="operator">|</span> <span class="literal">null</span> <span class="operator">-&gt;</span> <span class="built_in">failwith</span> <span class="string">&quot;...&quot;</span></span><br><span class="line">  <span class="operator">|</span> it <span class="keyword">when</span> it.Events <span class="operator">|&gt;</span> isEmpty <span class="operator">|&gt;</span> <span class="built_in">not</span> <span class="operator">-&gt;</span> </span><br><span class="line">    this.SaveEvents it.Events</span><br><span class="line">    this.CleanEvents ()</span><br><span class="line">  <span class="operator">|</span> _ <span class="operator">-&gt;</span> ()</span><br><span class="line"></span><br><span class="line">  db.Save it</span><br></pre></td></tr></table></figure>
+
+<p>在<code>Save()</code>方法中，首先获取到聚合根中的所有领域事件，然后通过<code>SaveEvents()</code>方法将它们保存到发布事件表中，最后通过<code>db.Save it</code>保存聚合根。需要注意的是，在这种方式下，<code>AggregateRoot</code>中的<code>events</code>字段是不能被持久化的，因为需要保证每次从数据库中加载出聚合根时<code>events</code>都是空的，为此在<code>SaveEvents()</code>保存了领域事件后，立即调用<code>it.clearEvents()</code>将所有的领域事件清空掉，以免领域事件随着聚合根一道被持久化到数据库中。</p>
+<p>到目前为止，对领域事件的处理都还没有涉及到与任何消息中间件相关的内容，也即事件的产生是一个完全独立于消息队列的关注点，此时不用关心领域事件之后将以何种形式发布出去，Kafka 也好，RabbitMQ 也罢。除了关注点分离的好处外，这种解耦也使得系统在有可能切换消息中间件时更加的简单。</p>
+<p>对于“在应用服务中通过<code>eventPublisher.Publish()</code>直接发布事件”而言，事件的产生和发布是同时完成的；但是对于“在聚合根中临时性保存领域事件”的方式来说，它只解决了事件的产生问题，并未解决事件的发布问题，事件的发布方应该采用“发射后不管(Fire And Forget)”的原则，即发布方无需了解消费方是如何处理领域事件的，甚至都不需要知道事件被哪些消费方所消费。</p>
+<p>但是因为发送事件需要操作消息中间件，而更新事件状态需要操作数据库。在不使用分布式事务的情况下，此时的代码对于“事件发布成功 + 数据库落库成功”来讲是皆大欢喜的，但是依然无法排除有很小的概率导致事件发送成功了但是状态却为得到更新的情况。要解决这个问题，有一个选择是做妥协，即事件发布方无法保证事件的“<a target="_blank" rel="noopener" href="https://www.cloudcomputingpatterns.org/exactly_once_delivery/">精确一次性投递(Exactly Once)</a>”，而是保证“<a target="_blank" rel="noopener" href="https://www.cloudcomputingpatterns.org/at_least_once_delivery/">至少一次投递（At Least Once）</a>”。假设在事件发布成功之后，由于种种原因导致事件的状态未得到更新，即依然为<code>CREATED</code>状态，那么稍后，当事件兜底机制启动时，它将加载系统中尚未发布的事件进行发布，其中就包含状态为<code>CREATED</code>的事件，进而导致事件的重复投递。</p>
+<p>“至少一次投递”将更多的负担转嫁给了事件的消费方，使得事件发送方得以全身而退。</p>
+<p>事件消费的重点在于如何解决发布方的“至少一次投递”问题。举个例子，假设在电商系统中，订单子系统发布了“订单已成交”（<code>OrderPlacedEvent</code>）事件，积分子系统消费这个事件时会给用户新增与订单价格等额的积分，但是对事件的“至少一次投递”有可能导致该事件被重复投递进而导致重复给用户积分的情况产生。解决这个问题通常有2种方式：</p>
+<ol>
+<li>将消费方自身的处理逻辑设计为幂等的，即多次执行和一次执行的结果是相同的</li>
+<li>消费方在数据库中建立一个事件消费表，用于跟踪已经被消费的事件</li>
+</ol>
+<p>第一种方式是最理想的，消费方不用引入额外的支撑性机制，但是这种方式对消费方的要求太高，并不是所有场景都能将消费方本身的处理逻辑设计为幂等。因此，实践中主要采用第二种方式。</p>
+
+</div> 
+
+<script>
+    window.onload = detectors();
+</script>
+    <div class="post-footer">
+    <div class="h-line-primary"></div>
+    <nav class="post-nav">
+        <div class="prev-item">
+           
+        </div>
+        <div class="next-item">
+            
+                <div class="icon arrow-right"></div>
+                <div class="post-link">
+                  <a href="/2025/03/17/%E4%BA%8C%E3%80%87%E4%BA%8C%E4%BA%94%E5%B9%B4%E4%B8%89%E6%9C%88%E5%8D%81%E4%B8%83%E6%97%A5/">Next</a>  
+                </div>  
+            
+        </div>
+    </nav>
+</div>
+
+    
+      <div class="post-comment">
+
+     
+
+     
+    
+    
+
+</div>
+     
+  
+</article>
+        </div>
+      </div>
+      
+      <div class="footer">
+    <div class="flex-container">
+        <div class="footer-text">
+            
+            
+                 | 
+            
+            
+                希望路过的人可以添点柴火让这里暖和点
+                
+        </div>
+    </div>
+</div>
+
+    </div>
+
+    
+      <div class="search-popup">
+    <div class="search-popup-overlay">  
+    </div>
+    <div class="search-popup-window" >
+        <div class="search-header">
+            <div class="search-input-container">
+              <input autocomplete="off" autocapitalize="off" maxlength="80"
+                     placeholder="Search Anything" spellcheck="false"
+                     type="search" class="search-input">
+            </div>
+            <div class="search-close-btn">
+                <div class="icon close-btn"></div>
+            </div>
+        </div>
+        <div class="search-result-container">
+        </div>
+    </div>
+</div>
+
+<script>
+    const searchConfig = {
+        path             : "/search.xml",
+        top_n_per_article: "1",
+        unescape         : "false",
+        trigger: "auto",
+        preload: "false"
+    }
+</script>
+<script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/search.js"></script>
+<script src="/js/search.js"></script>
+    
+    
+
+  </body>
+</html>