<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Super</title>
    <description/>
    <link>https://speakerdeck.com/superlede</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/superlede.rss"/>
    <lastBuildDate>2026-11-16 10:21:02 -0500</lastBuildDate>
    <item>
      <title>Per-customer API rate limiting</title>
      <description>What to key a limit on when you charge for an API, why rate limits and quotas need different answers, four common algorithms and their trade-offs, and how to count usage so it can be billed.

The longer write-up, with response headers and code: &lt;a href="https://usagerail.com/api-rate-limiting"&gt;API rate limiting algorithms and headers&lt;/a&gt;.</description>
      <media:content url="https://files.speakerdeck.com/presentations/f841df9bb8b64298bb9677cf5be21214/preview_slide_0.jpg?41396495" type="image/jpeg" medium="image"/>
      <content:encoded>What to key a limit on when you charge for an API, why rate limits and quotas need different answers, four common algorithms and their trade-offs, and how to count usage so it can be billed.

The longer write-up, with response headers and code: &lt;a href="https://usagerail.com/api-rate-limiting"&gt;API rate limiting algorithms and headers&lt;/a&gt;.</content:encoded>
      <pubDate>Mon, 16 Nov 2026 00:00:00 -0500</pubDate>
      <link>https://speakerdeck.com/superlede/per-customer-api-rate-limiting</link>
      <guid>https://speakerdeck.com/superlede/per-customer-api-rate-limiting</guid>
    </item>
    <item>
      <title>Postgres restore drills: proving your backups actually restore</title>
      <description>Why a backup job that exits 0 proves little, how to restore a pg_dump into a throwaway Postgres and check what came back, and the pg_restore errors that catch people out.

The longer write-up, with each step and the errors it runs into: &lt;a href="https://backupdrill.com/guides/test-supabase-backup-restore"&gt;how to test that a Supabase backup actually restores&lt;/a&gt;.</description>
      <media:content url="https://files.speakerdeck.com/presentations/0d3295a6d1904ad682d37312c8f817ed/preview_slide_0.jpg?41396460" type="image/jpeg" medium="image"/>
      <content:encoded>Why a backup job that exits 0 proves little, how to restore a pg_dump into a throwaway Postgres and check what came back, and the pg_restore errors that catch people out.

The longer write-up, with each step and the errors it runs into: &lt;a href="https://backupdrill.com/guides/test-supabase-backup-restore"&gt;how to test that a Supabase backup actually restores&lt;/a&gt;.</content:encoded>
      <pubDate>Mon, 16 Nov 2026 00:00:00 -0500</pubDate>
      <link>https://speakerdeck.com/superlede/postgres-restore-drills</link>
      <guid>https://speakerdeck.com/superlede/postgres-restore-drills</guid>
    </item>
  </channel>
</rss>
