aiohttp
Ranked 8 of 11 HTTP client libraries by recommenders
Python async HTTP library people recommend for its speed in benchmarks and over HTTPX; the main caveat is that it is tied to HTTP/1.
Python async HTTP library people recommend for its speed in benchmarks and over HTTPX; the main caveat is that it is tied to HTTP/1.
7 people gave an opinion
- recommend it
- 7
- criticize it
- 0
- approval share
- 100%
Recommended in 5 of 13 months
- November 2025: not recommended
- December 2025: recommended
- January 2026: not recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: not recommended
- May 2026: recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 7 people recommend itNeeds 10 or more, not met.
- Nobody criticizes itNeeds 2 to 1 or better, met.
- Recommended in 5 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Fast async performance
“Even frameworks written in JS (hyperexpress, just-js) or python (aiohttp) can vault into the realm of top-10 performers”
Comment from 24 Mar 2026 in “Sunsetting the Techempower Framework Benchmarks” “from your benchmarks it seems like I should've went with aiohttp for faster async”
Comment from 14 Dec 2025 in “Ask HN: What Are You Working On? (December 2025)” “I would advise everyone to switch to Aiohttp.”
Comment from 25 Mar 2026 in “I Forked Httpx” - Comment from 28 Aug 2026 in “HTTPX2 – A next-generation HTTP client for Python”
Preferred over HTTPX
“I would advise everyone to switch to Aiohttp.”
Comment from 25 Mar 2026 in “I Forked Httpx” “how much worse HTTPX performs versus Aiohttp”
Comment from 28 Aug 2026 in “HTTPX2 – A next-generation HTTP client for Python”
What people warn about
Each mark is one comment
Tied to HTTP/1
“it's too heavily tied to HTTP/1”
Comment from 25 Mar 2026 in “I Forked Httpx”
Other HTTP client libraries people recommend
The four most recommended other HTTP client libraries, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Requests (Python library) | 23 | 7 | 77% | 8 | — | Approved |
| Axios | 21 | 37 | 36% | 5 | — | — |
| Go net/http | 12 | 7 | 63% | 4 | — | — |
| libcurl | 10 | 2 | 83% | 7 | — | Approved |
| aiohttpThis page | 7 | 0 | 100% | 5 | — | — |
What people said
All 8 comments that mention it, newest first. Each links to the original comment.
“how much worse HTTPX performs versus Aiohttp”
“Those services were recreating HTTP clients (aiohttp) for every inbound request”
“it's too heavily tied to HTTP/1”
“I would advise everyone to switch to Aiohttp.”
“Even frameworks written in JS (hyperexpress, just-js) or python (aiohttp) can vault into the realm of top-10 performers”
“we got aiohttp (async only) and httpx”
“Switching to other libraries like requests and aiohttp and supporting them by contributing is clearly a better option.”
“from your benchmarks it seems like I should've went with aiohttp for faster async”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.