Philsturgeon.uk Website Review

platform engineer @ wework who talks about apis a lot. programming polyglot, pragmatist, centerist and sarcasist. ex-the league of. extraordinary packages, php the right way, ex-php-fig, ex-codeigniter, ex-fuelphp, ex-pyrocms. 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 layer of abstractions on top of rpc… more abstractions does not mean definitively better, sometimes that's going to be overkill, so let's look at when you might want to use which. 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 solutions. one of those solutions is a tangible thing, which you can install right now! the other is now ready for tool vendors to start 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. 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 the partial bits of functionality. 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