Post details
Why I still enjoy using GraphQL after 8 years
Why I still enjoy using GraphQL after 8 years
GraphQL is an incredible piece of technology that has captured a lot of mindshare since I first started slinging it in production in 2018. You won’t have to ...
You can now interact with dependency-management-data using GraphQL (2 mins read).
Announcing the release of the GraphQL API for dependency-management-data.
Prefer using the GitHub Software Bill of Materials (SBOMs) API over the Dependency Graph GraphQL API (2 mins read).
Why you should use GitHub's Software Bill of Materials API instead of the Dependency Graph GraphQL API.
Listing all GitHub repositories in a GitHub Organisation (3 mins read).
How to use the GraphQL API to list all the repositories that can be found in a given GitHub organisation.
A query language for your API — GraphQL provides a complete description of the data in your API, gives clients the power to ask for exactly what they need and nothing more, makes it easier to evolve APIs over time, and enables powerful developer tools.
GraphQL is a trap
Jeff Hodges (@jmhodges)Thu, 05 May 2022 18:31 +0000
Moving from a GraphQL product to a REST based product is the prime time for noticing all the things that are GoodActually™ about GraphQL
Joe Hart 🏳️🌈 (@JoeHart)Wed, 30 Mar 2022 10:16 +0000
GraphQL APIs are not an excuse to write zero documentation.
Jon Kuperman (@jkup)Sat, 20 Nov 2021 23:14 GMT
The biggest difference between REST and GraphQL is that when you build GraphQL API nobody tells you "well, actually this is not GraphQL".
Maciej Walkowiak 🍃 (@maciejwalkowiak)Fri, 08 Oct 2021 00:57 +0000
Beyond Rest: The Future of Web APIs (8 mins read).
A writeup of the meetup talking about what could come next for APIs.
You're currently viewing page 1 of 1, of 13 posts.