Skip to content

Site comparison: split into topic-specific tables (API-client / mocking / security), add WireMock + Mockito, broaden beyond top-5 #413

Description

@thomas-stegemann

Problem

The site has exactly one tool-vs-tool comparison — a hand-authored top-5 matrix in site/_includes/comparison.html (rendered on the homepage via index.html). It is framed entirely around the API-client / workbench category — discovery + invocation + streaming/logging + record/replay:

  • Competitors in the scored matrix: Postman, Scalar, Swashbuckle, Insomnia, Bruno (grpcui/grpcurl only appears in the prose strip). Footnote: "The table below is the exhaustive top-5-competitors check."
  • Section subtitle: "Postman, Scalar, Swashbuckle, Insomnia, Bruno — every API tool has its sweet spot."

Two problems with that single frame:

  1. Mocking and security are jammed in as single rows (Replay as mock server, Security scanning) inside an API-client matrix, so they're only ever compared against Postman/Insomnia's mock/secret features — never against the actual peer tools in those categories.
  2. The relevant peers are absent. For mocking there is no WireMock, Mockito, MockServer, Prism, Microcks, Hoverfly, Mountebank; for security no ZAP/Burp/Schemathesis. A reader evaluating Bowire as a mock server or as a scanner gets no comparison at all.

The top-5 API-client matrix is the right comparison for the discovery/invocation/logging story — it's just being asked to carry topics it wasn't designed for.

Proposal

Split the single matrix into topic-specific comparisons, aligned with the site's own IA (site/solutions.html: a solution is the what/what-for — the topic). The topic pages already exist under site/solutions/.

  1. Keep the homepage matrix as the API-client / workbench comparison — and broaden it beyond 5 (candidates: Hoppscotch, Kreya, Thunder Client, grpcui/grpcurl as a real column, apidog).
  2. Add a mocking comparison on solutions/service-mocking.html. Important nuance so it isn't apples-to-oranges:
    • Service / API mocking = Bowire's actual peers: WireMock, MockServer, Prism (Stoplight), Microcks, Hoverfly, Mountebank, Beeceptor, json-server. This is where Bowire directly competes (see epic Mock-server maturity — WireMock feature parity (epic) #401 for the WireMock feature-gap analysis).
    • Unit / object mocking = Mockito (JVM), Moq / NSubstitute / FakeItEasy (.NET). These are a different layer — Bowire is not a unit-mocking framework. Include them explicitly but frame them as adjacent, not replaced: a short "Bowire mocks the service over the wire; Mockito/Moq mock objects inside a test process — complementary, not competing" note. This answers the reader who lumps all "mocking" together without implying a false equivalence.
  3. Add a security comparison on solutions/security.html (stretch): Bowire scan/fuzz vs OWASP ZAP, Burp, Schemathesis, Nuclei — instead of the current single row that only lines up against Postman's secret scanner.

Enabler (tech-debt)

The comparison is hand-authored HTML whose columns must stay in lockstep across three places: the <table> in comparison.html, the tools array in assets/js/main.js (~L254-260), and nth-child selectors in assets/css/style.css (~L4292-4301) (the code comments call out the required sync). Adding tools/topics under this scheme is fragile and expensive.

Refactor the comparison into a _data/*.yml-driven structure (tools list + axis definitions + per-cell state yes|partial|no + optional detail/label) that a single templated include iterates over, per topic (_data/compare-clients.yml, _data/compare-mocking.yml, _data/compare-security.yml). This removes the triple-sync fragility and makes "add WireMock", "add Mockito", "add a column" one-line data edits. Do this first; the topic tables fall out of it.

Acceptance

  • Comparison refactored to a _data-driven templated include (removes HTML/JS/CSS triple-sync)
  • Homepage API-client matrix broadened beyond the current 5 tools
  • Mocking comparison on solutions/service-mocking.html incl. WireMock (+ MockServer / Prism / Microcks / Hoverfly / Mountebank) and a clearly-delineated unit-mocking row for Mockito / Moq / NSubstitute framed as adjacent-not-replaced
  • Security comparison on solutions/security.html (ZAP / Burp / Schemathesis / Nuclei) (stretch)
  • Axes chosen per topic (a mocking table's axes = request matching, response templating, stateful scenarios, protocols mocked, verify, proxy, deploy — cf. Mock-server maturity — WireMock feature parity (epic) #401), not the API-client axes reused verbatim
  • Homepage still links out to the topic-specific comparisons

Refs

Metadata

Metadata

Labels

No labels
No labels

Projects

  • Status
    Backlog

Relationships

None yet

Development

No branches or pull requests

Issue actions