In Part 1 we looked at how APIs have evolved over the last few decades and how each one gave way to the next. We also talked about some of the particular drawbacks of using REST for mobile client development. In this article, I want to look at where mobile client API design appears to be headed — with a particular emphasis on GraphQL. There are, of course, lots of people, companies, and projects that have tried to address RESTs shortcomings over the years: HAL, Swagger/OpenAPI, OData JSON API and dozens of other smaller or internal projects have all sought to bring order to the spec-less world of REST.
from Articles on Smashing Magazine — For Web Designers And Developers https://www.smashingmagazine.com/2018/01/graphql-primer-new-api-part-2/
from Articles on Smashing Magazine — For Web Designers And Developers https://www.smashingmagazine.com/2018/01/graphql-primer-new-api-part-2/
Comments
Post a Comment