Phil Sturgeon

A while back I wrote an article called Understanding RPC, REST and GraphQL which outlined the “what” in how these various approaches differ…

API Evolution is making a comeback these days with GraphQL and gRPC advocates shouting about it. Whatever API paradigm or implementation you subscribe to, evolution is available to you. REST advocates have been recommending API evolution for decades, so let's take a look at how that can work.

Update 2020-02-02: This article has been replaced entirely, as the proposed workaround was written into a now abandoned project Speccy, and…

This article is going to explain the divergence between OpenAPI and JSON Schema, which I’ve been calling the subset/superset/sideset problem…

Back in October I wrote Chasing the Perfect API Specification Workflow, which was a huge article about the state of the API specification…

The misunderstandings on REST continue, and I'm happy to explain them all up!

This article outlines a list of common misunderstandings about REST, so I thought it would be a nice opportunity to set the record straight on a bunch of them. The article is really just 100% misunderstandings, so lets learn some stuff!

Last month today OpenAPI v3.0 was released, and not only is there a lot of cool stuff, but it unblocks some akward situations with vendor…

With endpoint-based APIs you get to choose if you want increased likelihood of network cache hits, or the ability to slim down the response. The two goals are mutually exclusive, but there is a compromise that can be made.

Documentation is a nice thing to have, but it is often treated as optional or superfluous, especially in teams where the clients and servers…

It's very common for APIs to be treated like "databases over HTTP", with clients expected to infer state from a collection of boolean switches and date fields. Stop this with HATEOAS.

After writing about how GraphQL and REST differ in various regards, and taking a closer look at caching in particular, I wanted to write…