GraphQL First, or “schema first”, development is a concept that was unveiled about a year ago when the Apollo Dev team first published an article about it and then described it in detail at GraphQL Summit in San Francisco
Everyday GraphQL First in action In there, when either a front-end or back-end developer wants to suggest some changes to the schema, we create a pull-request that adds a [feature.faker.graphql] file. We can then use the normal GitHub review process to provide feedback, approval or ask for some modifications. Both the front-end and back-end teams have to approve the changes for it to be merged and then implemented.
Let’s have a look at that development workflow. For that use case, we will assume I’m an engineer looking at some product specifications: we want to add to the user page a profile picture. We should be able to see a thumbnail, and, when clicking on the picture, the full-size image.
GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data. It provides a complete and understandable description of the data in your API as well as gives clients the power to ask for exactly what they need and nothing more. It was developed by Facebook as an internal solution for their mobile apps and was later open-sourced to the community. In this post, I share my thoughts on good practices for creating a GraphQL server
CRUD Tutorial - React, GraphQL, NodeJS, MySQL. Tech Stack: - ReactJS - NodeJS - ExpressJS - GraphQL / Express GraphQL / Apollo Client - TypeScript - MySQL - TypeOrm
GraphQL Finland has a different scope, and it's going to be the first Nordic GraphQL focused conference. I'm looking forward to seeing everyone interested in GraphQL at the event.
Today, we launched our event site for GraphQL Summit, the first-ever GraphQL conference. Be sure to check out the full site to see what’s in store.