So you’ve kicked the tires and decided GraphQL is a good approach for your project. Now you’re staring at an empty editor window, pondering on how to structure your code. The GraphQL docs are a great resource for whetting the appetite, but doesn’t (and shouldn’t) offer much project-specific guidance. The Apollo documentation, while library specific, offers a wealth of information and some solid strategies. What follows is some opinionated commentary on successes and failures from the first 4 large projects I’ve built with Node.js.
One of the biggest problems with most APIs is that they’re lacking strong contracts for what their operations look like. Many developers have found themselves in situations where they needed to work with deprecated API documentation, lacking proper ways of knowing what operations are supported by an API and how to use them.