A Performance and Scalability Evaluation of Monolithic (Django) vs. Microservice (FastAPI) Architectures for Asynchronous API Workloads in Python

2026

Closed access Metadata (CSL-JSON)
DOI 10.1109/icecco67619.2026.11488798
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

As few empirical performance comparisons of modern Python web frameworks exist, it is hard to choose an appropriate architecture under real I/O-bound workloads. This study compares a monolithic back-end implemented with Django, a popular framework implementing the model-view-template software design pattern, with a microservice back-end built using FastAPI. Running load tests using Apache JMeter inside a Docker container indicated a several-fold improvement in performance with the microservice architecture. FastAPI, in a microservice architecture, yielded more than 6 times the throughput of the monolithic Django architecture: 67.8 req/sec versus 10.1 req/sec. Additionally, FastAPI had a significantly lower average latency with the same 0.00% error rate. The empirical results of this work show that for I/O-bound applications, a modern asynchronous microservice architecture can provide much better performance and scalability than a customary monolithic architecture.