<?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>AIInfra on Mengboy Tech Notes</title>
    <link>https://www.mfun.ink/en/categories/aiinfra/</link>
    <description>Recent content in AIInfra on Mengboy Tech Notes</description>
    <generator>Hugo -- 0.156.0</generator>
    <language>en</language>
    <lastBuildDate>Wed, 01 Apr 2026 01:19:20 +0000</lastBuildDate>
    <atom:link href="https://www.mfun.ink/en/categories/aiinfra/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Claude 3.7 &#43; OpenAI Responses Dual-Stack Degradation Playbook: Timeout Probing, Circuit Cutover, and Error-Budget Dashboard</title>
      <link>https://www.mfun.ink/en/2026/04/01/claude-openai-dual-stack-degrade-runbook/</link>
      <pubDate>Wed, 01 Apr 2026 01:19:20 +0000</pubDate>
      <guid>https://www.mfun.ink/en/2026/04/01/claude-openai-dual-stack-degrade-runbook/</guid>
      <description>&lt;p&gt;Running both Claude and OpenAI in production sounds resilient—until a &lt;strong&gt;slow failure&lt;/strong&gt; hits: latency climbs, 429s spike, quality drifts, and everything still looks “up.”&lt;/p&gt;
&lt;p&gt;This guide gives you a practical dual-stack degradation runbook: timeout probing first, circuit-based cutover second, and an error-budget dashboard to keep business impact bounded.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Claude &#43; OpenAI Dual-Provider Gateway Failover: Health Probes, Circuit Breaking, and SLA Fallback</title>
      <link>https://www.mfun.ink/en/2026/03/30/claude-openai-dual-provider-gateway-failover-sla/</link>
      <pubDate>Mon, 30 Mar 2026 01:14:00 +0000</pubDate>
      <guid>https://www.mfun.ink/en/2026/03/30/claude-openai-dual-provider-gateway-failover-sla/</guid>
      <description>&lt;p&gt;If your production stack calls both Claude and OpenAI, the hard part is not API integration. The hard part is keeping user experience stable when one provider starts throwing 429/5xx spikes, regional latency, or timeout storms.&lt;/p&gt;
&lt;p&gt;This guide gives you a practical dual-provider gateway playbook: health probes, circuit breaking, SLA-aware fallback, and observability loops. The goal is not “never fail.” The goal is &lt;strong&gt;controlled failure with controlled cost and controlled latency&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
