<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - HTTP</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ HTTP feed</description>
    <item>
      <title>Article: Using AWS Lambda Extensions to Run Post-Response Telemetry Flush</title>
      <link>https://www.infoq.com/articles/lambda-extension-deferred-flush/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=HTTP</link>
      <description>&lt;img src="https://res.infoq.com/articles/lambda-extension-deferred-flush/en/headerimage/lambda-extension-deferred-flush-header-1775648097720.jpg"/&gt;&lt;p&gt;At Lead Bank, synchronous telemetry flushing caused intermittent exporter stalls to become user-facing 504 gateway timeouts. By leveraging AWS Lambda's Extensions API and goroutine chaining in Go, flush work is moved off the response path, returning responses immediately while preserving full observability without telemetry loss.&lt;/p&gt; &lt;i&gt;By Melvin Philips&lt;/i&gt;</description>
      <category>Serverless</category>
      <category>API Gateway</category>
      <category>AWS</category>
      <category>API</category>
      <category>HTTP</category>
      <category>Cloud</category>
      <category>AWS Lambda</category>
      <category>Development</category>
      <category>DevOps</category>
      <category>article</category>
      <pubDate>Wed, 15 Apr 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/lambda-extension-deferred-flush/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=HTTP</guid>
      <dc:creator>Melvin Philips</dc:creator>
      <dc:date>2026-04-15T09:00:00Z</dc:date>
      <dc:identifier>/articles/lambda-extension-deferred-flush/en</dc:identifier>
    </item>
    <item>
      <title>Article: Stateful Continuation for AI Agents: Why Transport Layers Now Matter</title>
      <link>https://www.infoq.com/articles/ai-agent-transport-layer/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=HTTP</link>
      <description>&lt;img src="https://res.infoq.com/articles/ai-agent-transport-layer/en/headerimage/ai-agent-transport-layer-header-1775031603285.jpg"/&gt;&lt;p&gt;Agent workflows make transport a first-order concern. Multi-turn, tool-heavy loops amplify overhead that is negligible in single-turn LLM use. Stateful continuation cuts overhead dramatically. Caching context server-side can reduce client-sent data by 80%+ and improve execution time by 15–29% .&lt;/p&gt; &lt;i&gt;By Anirudh Mendiratta&lt;/i&gt;</description>
      <category>OpenAI</category>
      <category>WebSocket</category>
      <category>AI Coding</category>
      <category>HTTP</category>
      <category>AI Assisted Coding</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>article</category>
      <pubDate>Wed, 08 Apr 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/ai-agent-transport-layer/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=HTTP</guid>
      <dc:creator>Anirudh Mendiratta</dc:creator>
      <dc:date>2026-04-08T09:00:00Z</dc:date>
      <dc:identifier>/articles/ai-agent-transport-layer/en</dc:identifier>
    </item>
  </channel>
</rss>
