4 micro-topics in Services & APIs, each with the evidence that proves you have it and the written reason behind every link. Before you start, it rests on 2 other domains. Downstream, it holds up 5 domains.
4 topics · depth 3–5 of 16 · 3 internal links · 3 in · 6 out
Load-bearing links first. Each one says what in this domain rests on what outside it, and why.
2 links
Design an API contract rests on Return correct status codes
A contract specifies responses including failures.
Design error responses rests on Return correct status codes
Error responses carry status codes.
1 link
Design an API contract rests on Model one-to-many and many-to-many
Resource shapes usually mirror the data model.
In prerequisite order. Each idea names the artifact that closes it, the market demand that put it on the map, and what it stands on.
Depth 3 · representational · scaffolded · M07 §7.2
Specifies resources, shapes and errors before code
Return correct status codes · HTTP
A contract specifies responses including failures.
Model one-to-many and many-to-many · Data Modeling
Resource shapes usually mirror the data model.
Depth 4 · representational · unassisted · M16 §16.2
Writes and generates an OpenAPI 3.1 specification
The specification expresses a contract.
Depth 4 · representational · unassisted · M16 §16.2
Returns machine-readable, actionable errors
Error shapes are part of the contract.
Return correct status codes · HTTP
Error responses carry status codes.
Depth 5 · conceptual · scaffolded · M16 §16.2
Evolves a contract without breaking clients
Versioning evolves a published specification.
Everything downstream that names an idea here as a prerequisite, grouped by where it lives.
1 link
Keep types safe across the stack rests on Express a contract in OpenAPI
Generated clients come from a specification.
1 link
Document an API rests on Design an API contract
You document a contract you have designed.
1 link
Declare tools for a model rests on Design an API contract
A tool declaration is a contract for the model.
2 links
Validate at the boundary rests on Design an API contract
The boundary is where the contract is enforced.
Generate JSON Schema from models rests on Express a contract in OpenAPI
Generated schema is what makes the spec trustworthy.
1 link
Handle errors mid-stream rests on Design error responses
Error design carries over, but the response has already begun.
Retool. Retrain. Relaunch.
375 ideas. 17 weeks. No tuition, ever.
Vets Who Code is a veteran-run 501(c)(3). The accelerator is free, remote, and we don’t take a share of your first paycheck.
Free · Remote · 17 weeks · EIN 86-2122804