José Miguel Gómez

Back to the home page

Aforo

One contract and conformance suite for ten polyglot booking APIs

Status
Coming soon
Type
Developer tool
Running since
November 2026
Role
Architect and sole engineer
Domains
API design, contract testing, concurrency, reference architecture
Cast
OpenAPI, JSON Schema, Hurl, Schemathesis, Java, Spring Boot, Csharp, Aspnetcore, Go, Gin, Ruby, Rails, React, Angular

Context and problem

One API contract, four implementations (Spring Boot, ASP.NET Core, Go, Rails), 379/379 cases each.

Comparing stacks without a shared, executable spec is anecdote: RealWorld-style apps have no invariant that can break under concurrency. The Aforo suite fires 300 simultaneous clients at a 50-seat event.

Screens

How it was built

Built in 13.95 h across 5 repos · conformance 379/379 each

Source: Each repository states its own figures: r1 1.95 h, USD 65.77, 403 tests; L01 3.50 h, USD 54.84; L02 2.10 h; L04 4.40 h, USD 40.46; L08 2.00 h (L02 and L08 cost not computed), dated 21 November 2026.

Results with dated evidence

Outcomes as stated in the manifest; the measured figures are the ones with a date.

  • Full Aforo conformance profile 379/379 on contract 2.0.0 in Spring Boot (L01), ASP.NET Core (L02), Go (L04) and Rails (L08).
  • L04: own race with 500 goroutines through the HTTP API, exactly 50 confirmed, 25 waitlisted, 425 event-full.
  • L08: one process, two SQLite files; Litestream restores the data in 70 ms, verified by a hash of every row.
  • L09 React client: all 28 shared end-to-end scenarios pass on desktop and mobile against the reference implementation.

Case study in preparation

The full case study adds these sections when it is published:

  • Constraints
  • Architecture diagrams (C4 context and containers)
  • Three key decisions
  • What went wrong
  • Demo video
  • What I would do differently

Highlights

contract first, conformance suite, optimistic concurrency, polyglot