web-frameworks

<div align="center">

# 🚀 Web Frameworks Benchmark

**A community-maintained, reproducible comparison of backend web frameworks**

[Explore the results](https://web-frameworks-benchmark.netlify.app/) · [Add a framework](CONTRIBUTING.md) · [Report a problem](https://github.com/the-benchmarker/web-frameworks/issues) · [Join the discussion](https://github.com/the-benchmarker/web-frameworks/discussions)

[![CI](https://github.com/the-benchmarker/web-frameworks/actions/workflows/ci.yml/badge.svg)](https://github.com/the-benchmarker/web-frameworks/actions/workflows/ci.yml)
[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
[![GitHub stars](https://img.shields.io/github/stars/the-benchmarker/web-frameworks?style=flat)](https://github.com/the-benchmarker/web-frameworks/stargazers)
[![Contributors](https://img.shields.io/github/contributors/the-benchmarker/web-frameworks)](https://github.com/the-benchmarker/web-frameworks/graphs/contributors)

</div>

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](.spec/route_spec.rb) 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
<language>/config.yaml       # language image, runtime, and engine settings
<language>/<framework>/config.yaml
                             # framework version, files, command, and overrides
```

## 📊 Results

The latest published results are available on the [Web Frameworks Benchmark dashboard](https://web-frameworks-benchmark.vercel.app). Each result should be read in the context of its framework version, runtime or server variant, concurrency, benchmark revision, and