From Learning Clientside GraphQL with Apollo by Azat Mardan
From Learning Clientside GraphQL with Apollo
By Azat Mardan
From The Design of Everyday APIs by Arnaud Lauret
Why should we care about the design of an API? It’s quite simple. What do you do when you use an everyday thing, whether it’s a microwave oven, a web site, a mobile application, a TV remote or an ATM? You use its interface.
From The Design of Everyday APIs
By Arnaud Lauret
From GraphQL in Motion
By Tyler Reckart
Chapters selected by Justin Richer and Antonio Sanso
From Irresistible APIs
By Kristen Hunter
From Irresistible APIs by Kirsten L. Hunter
In general, companies and organizations want to keep their vision and strategy close to the chest. Revealing this sort of information outside of your development organization feels like a vulnerable choice, but it is critical for a new platform, or an existing platform, to provide as much context around the API program as possible. I’m not talking here about reference documentation, tutorials, and example code. For this high level communication I’m talking about things like the overall vision, business values, and metrics.
By Evan Hahn
What if you decide down the road that you want to update your API without having all of the people who use your API have to update their code? In this article, excerpted from Express in Action, I’ll talk about versioning your API.
