<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>V8 on Laputa</title>
    <link>https://chenjianyong.com/tags/v8/</link>
    <description>Recent content in V8 on Laputa</description>
    <generator>Hugo</generator>
    <language>en-GB</language>
    <lastBuildDate>Sun, 07 Sep 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://chenjianyong.com/tags/v8/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Durable Object Write Coalesce</title>
      <link>https://chenjianyong.com/blog/2025/durable-object-write-coalesce/</link>
      <pubDate>Sun, 07 Sep 2025 00:00:00 +0000</pubDate>
      <guid>https://chenjianyong.com/blog/2025/durable-object-write-coalesce/</guid>
      <description>&lt;p&gt;In the blog post &lt;a href=&#34;https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/&#34;&gt;Durable Objects: Easy, Fast, Correct — Choose Three&lt;/a&gt;, Kenton introduces two critical implementation concepts of Durable Objects: the input gate and the output gate. These mechanisms work in tandem to address data races and enable seamless in-memory caching, ensuring both correctness and performance.&lt;/p&gt;&#xA;&lt;p&gt;However, I&amp;rsquo;m particularly intrigued by another feature Kenton highlighted as a bonus of the output gate implementation: automatic write coalescing.&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;    &lt;p&gt;&amp;ldquo;First, writes are automatically coalesced. That is, if you perform multiple &lt;code&gt;put()&lt;/code&gt; or &lt;code&gt;delete()&lt;/code&gt; operations without &lt;code&gt;await&lt;/code&gt;ing them or anything else in between, then the operations are automatically grouped together and stored atomically.&amp;rdquo;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
