Written by Phil Sturgeon
/ Original link
on Aug. 22, 2019
Two months ago I teased that Stoplight was about to release something big, and yesterday we announced Stoplight Studio - an OpenAPI and standalone JSON Schema editor, which just so happens to be visually stunning and completely free. Studio runs as a web app or desktop app, can wor…
Written by Phil Sturgeon
/ Original link
on Jun. 13, 2019
This blog has been a bit quiet for the last two years, with me blogging on APIsYou Won’t Hate andphil.bike more than here.2017 was mostly spent putting out fires at WeWork as an API designer andarchitect, helping to debug and stabilize their tightly coupled deathstararchitecture,which was constantl…
Written by Phil Sturgeon
/ Original link
on Mar. 1, 2018
Back in October I wrote Chasing the Perfect API Specification Workflow, which was a huge article about the state of the API specification world. One person trying to figure out a good workflow, in a sea of alternative specifications, with incomplete tooling, making it hard to see a solution for all…
Written by Phil Sturgeon
/ Original link
on Mar. 30, 2018
This article is going to explain the divergence between OpenAPI and JSON Schema, which I've been calling the subset/superset/sideset problem. It'll finish up explaining how we're going to solve it, and ~I'll write part 2 when it is solved~ part two explains the solution.Whenever talking about API…
Written by Phil Sturgeon
/ Original link
on May. 22, 2018
A while back I wrote an article called Understanding RPC, REST and GraphQL which outlined the "what" in how these various approaches differ. This got a few people thinking I was saying REST was drastically superior in all ways, which is a common conclusion when folks hear me describe REST as a laye…
Written by Phil Sturgeon
/ Original link
on May. 21, 2018
A while back I wrote an article called Understanding RPC, REST and GraphQL which outlined the “what” in how these various approaches differ. This got a few people thinking I was saying REST was drastically superior in all ways, which is a common conclusion when folks hear me describe REST as a laye…