<?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>Dynamodb on Chris Zeng</title>
    <link>https://chris-zeng.pages.dev/tags/dynamodb/</link>
    <description>Recent content in Dynamodb on Chris Zeng</description>
    <image>
      <title>Chris Zeng</title>
      <url>https://chris-zeng.pages.dev/img/headshot.jpg</url>
      <link>https://chris-zeng.pages.dev/img/headshot.jpg</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 05 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://chris-zeng.pages.dev/tags/dynamodb/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>An Ops Win: Cutting DynamoDB&#39;s TLS Handshake Latency with AWS-LC</title>
      <link>https://chris-zeng.pages.dev/posts/dynamodb-tls-aws-lc/</link>
      <pubDate>Wed, 05 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://chris-zeng.pages.dev/posts/dynamodb-tls-aws-lc/</guid>
      <description>In 2022 I swapped the cryptographic library under DynamoDB&amp;rsquo;s TLS termination from OpenSSL 1.0.2 to AWS-LC and deployed it to every AWS region with zero downtime, on a database serving hundreds of billions of requests an hour. Median handshake time dropped 12–35% by region, and FIPS endpoints dropped as much as 80%. This is the internal ops-win announcement rewritten for the public, including what made it hard — modifying Nginx source against a new crypto API, a legacy build system, Amazon&amp;rsquo;s deployment machinery, and cryptography where mistakes are quiet — and the two ways the rollout bit back.</description>
    </item>
  </channel>
</rss>
