A Performance Evaluation of Flask (WSGI) and Fastapi (ASGI) Under High-Concurrency Workloads

Mohammed Alaa Ala’anzy, Zhandos Yeshpatov, Adil Akhmetov, Ramis Akhmedov, Omar Alnaseri

2026

Closed access Metadata (CSL-JSON)
DOI 10.1109/icecco67619.2026.11488817
Data confidence 70 medium
How this score is calculated

It is built from checkable properties of the record itself: whether the article has a DOI, how many independent sources confirmed its data, whether the required fields are filled in, and how recent the latest confirmation is. Disagreement between sources and a missing identifier lower it. A value of 80 or above means the record was published without further checking; 60 to 79 means it is published at reduced confidence, with a manual check advisable. A record verified by an editor by hand is never pushed below 90 by a recalculation. This scores our data about the article, not the article itself.

Abstract

Python web development is experiencing a paradigm shift from the traditional Synchronous Web Server Gateway Interface (WSGI) to the modern Asynchronous Server Gateway Interface (ASGI). While WSGI frameworks like Flask have existed for a long time as the industry standard for microservices, their blocking architecture inherently restricts performance under high-concurrency workloads. This research fills this specific gap completely by introducing a rigorous quantitative benchmark comparing Flask WSGI with FastAPI (ASGI). Through the construction of two functionally identical applications and rigorous controlled I/O-bound load testing using Apache JMeter, throughput, latency, and error rates are measured. Results show a stark contrast in stability; ASGI kept 100% reliability, WSGI failed by 76% under identical load. These findings have actionable implications for software developers that moving to asynchronous frameworks is not just an adaptation but a requirement in our current and high-throughput API environment.