<?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>Api-Design on Chris Zeng</title>
    <link>https://chris-zeng.pages.dev/tags/api-design/</link>
    <description>Recent content in Api-Design 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/api-design/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Phone Numbers as Cloud Resources: the Amazon Connect APIs I Worked On</title>
      <link>https://chris-zeng.pages.dev/posts/amazon-connect-phone-number-apis/</link>
      <pubDate>Wed, 05 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://chris-zeng.pages.dev/posts/amazon-connect-phone-number-apis/</guid>
      <description>At Amazon I designed, built, tested, and deployed public phone-number APIs for Amazon Connect — in Java, globally, to support Connect users provisioning numbers for their contact centers. A phone number looks like a string; in Connect it&amp;rsquo;s a cloud resource with an ARN, tags, an asynchronous provisioning workflow, and a quota rule that stops you from churning numbers. This is a tour of the API surface and the design decisions you can read in the contract itself.</description>
    </item>
  </channel>
</rss>
