A REST View of GraphQL
My main qualm about REST is the number of inputs for doing something: Path variables, query variables, POST input, headers and for shits and giggles the Http METHOD. To top it off, because people want &quot;beautiful&quot; REST APIs everyone has a playground to do these kinds of things differently. And boy are they done very differently from company to company. And that leads to massive opinionated people. Finally, REST is tied to HTTP too tightly. It can&#x27;t be independent of it, ever. I know a lot of people believe that&#x27;s a good thing, in that there are metrics, logs, and a variety of data that assists architecturally. But it has only reached that status because we&#x27;re sitting at 15 years of REST toolchains.<p>I&#x27;m not saying GraphQL is the long term answer, but personally I&#x27;d rather be in a project using GraphQL (and hopefully not backed by REST at all)