the-benchmarker /web-frameworks

Which is the fastest web framework?

★ 7,096⑂ 750👁 138⑃ 9,042● 1,259▤ 15
PHPMITCreated 2017-03-27web-frameworks-benchmark.vercel.app
Download: 2018.9.262018.9.26 ↓2018.9.262018-09-26
7,096
stars
750
forks
138
watchers
9,042
prs
1,259
issues
15
releases

README

🚀 Web Frameworks Benchmark

A community-maintained, reproducible comparison of backend web frameworks

Explore the results · Add a framework · Report a problem · Join the discussion








From established full-stack platforms to small HTTP routers, this repository puts hundreds of implementations behind the same tiny API and runs them in isolated containers. Today, it makes a focused part of web-stack performance easier to measure, reproduce, and discuss. The longer-term goal is a comprehensive, evidence-based guide that helps businesses choose a backend framework—not merely a leaderboard that declares one universal winner.

 [!IMPORTANT]
 These are minimal HTTP throughput and latency tests, not a substitute for profiling a production application. Framework features, maintainability, ecosystem, security, database access, and your real workload all matter.

 🧪 Benchmark contract

Every implementation is expected to listen on port 3000 and provide the same responses:

| Method | Route | Expected status | Expected body |
|:--|:--|:--:|:--|
| GET | / | 2xx | Empty |
| GET | /user/:id | 2xx | The id path parameter |
| POST | /user | 2xx | Empty |

Before an implementation is benchmarked, the shared RSpec contract verifies these routes. The default generated benchmark runs GET / for 15 seconds using zrk --closed and keep-alive, and records a JSON report. Concurrency and routes are configurable.

Collected fields include requests per second, total data received, run duration, and the p50, p75, p90, and p99 latency percentiles. Benchmark configuration is generated from three YAML layers:

text
config.yaml                   provider and global settings
/config.yaml        language image, runtime, and engine settings
//config.yaml
                              framework version, files, command, and overrides


 📊 Results

The latest published results are available on the Web Frameworks Benchmark dashboard. Each result should be read in the context of its framework version, runtime or server variant, concurrency, benchmark revision, and hardware.

For a fair interpretation:

- compare runs produced by the same benchmark revision and machine;
- check the selected runtime/server variant, not only the framework name;
- treat small differences as noise until repeated;
- do not extrapolate this minimal API test to database-heavy or full application workloads.

 🗺️ Roadmap

The project is evolving from a focused HTTP performance benchmark into a broader decision-support guide for organizations choosing a backend framework. The intended presentation is inspired by the clarity of quadrant-based market analysis, but the evaluation model will be designed specifically for backend frameworks and backed by transparent, reproducible evidence. This project is independent and is not affiliated with or endorsed by Gartner.

+ [ ] ⚡ Use a modern load generator, please follow discussion in https://github.com/the-benchmarker/web-frameworks/discussions/8088
+ [ ] 🔧 Optimize i

Top issues

Discussions

Latest release

2018.9.26 2018.9.26 2018-09-26
New frameworks

+ Quart A python web framework 351 388 @waghanza @pgjones
+ Beego A go web framework 386 @GNURub 
+ Prism A crystal web framework 340 342 @vladfaust @waghanza
+ http4s A scala web framework 359 356  @mfirry @waghanza
+ AIOHttp A python web framework 350 @greed2411
+ Bottle A python web framework 343 @greed2411 @waghanza

 Update

+ Fastify Update to 1.12 362 391 @waghanza
+ Polka Update to 0.5 374 375 383 @waghanza
+ Kitura Update to 2.5 385 @waghanza
+ Tornado Update to 5.1 380 @waghanza
+ Django Update to 2.1 370 @waghanza
+ Sanic Update to 0.8 371 @waghanza

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON