Multi-approach showcase Β· one contract
One article-CRUD API β identical HTTP behaviour behind one OpenAPI contract and one black-box conformance suite β built in ten architectures and runtimes. Pick an implementation to inspect it and call it live; read the charts to see what each approach costs.
Grouped by runtime. Each builds/typechecks clean and ships a Dockerfile + compose. When the stack is deployed, βOpen live API explorerβ calls the selected implementation through the shared contract.
Five .NET styles, identical behaviour and near-identical throughput. What differs is how much code each needs.
Different runtimes, so throughput and resource use are the point. Code size is context only β lines across languages don't compare directly. Real numbers land when the benchmark harness runs.
Source metrics only β tests, generated migrations and build output excluded.
| Implementation | Runtime | Axis | Files | Lines | Non-blank | req/s | p99 | Build |
|---|