<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Starlette on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/starlette/</link>
    <description>Recent content in Starlette on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 10 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/starlette/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Python Async Web Frameworks in 2026: aiohttp vs Starlette vs Sanic — Which One Should You Use?</title>
      <link>https://www.pistack.xyz/posts/2026-08-10-python-async-web-frameworks-aiohttp-starlette-sanic/</link>
      <pubDate>Mon, 10 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-08-10-python-async-web-frameworks-aiohttp-starlette-sanic/</guid>
      <description>&lt;h2 id=&#34;the-gil-is-not-your-bottleneck-anymore&#34;&gt;The GIL Is Not Your Bottleneck Anymore&lt;/h2&gt;&#xA;&lt;p&gt;A typical Flask service spends 90% of its request time waiting on a database, a cache, or an upstream API — and every one of those seconds pins a thread that could have served a hundred other requests. Asyncio changed that: with cooperative concurrency, one event loop multiplexes thousands of in-flight requests across a handful of threads. The hard part is choosing the framework. &lt;strong&gt;aiohttp&lt;/strong&gt;, &lt;strong&gt;Starlette&lt;/strong&gt;, and &lt;strong&gt;Sanic&lt;/strong&gt; are the three serious async-native options in Python, and despite overlapping feature sets, they target fundamentally different users.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
