Multi-approach showcase Β· one contract

The same API, ten ways.

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.

Choose an implementation

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.

API explorer

Axis A β€” code ceremony (.NET, same runtime)

Five .NET styles, identical behaviour and near-identical throughput. What differs is how much code each needs.

Axis B β€” performance by runtime

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.

Code size by runtime Β· lines, context

All implementations

Source metrics only β€” tests, generated migrations and build output excluded.

ImplementationRuntimeAxisFilesLinesNon-blankreq/sp99Build