My boss described GraphQL today without knowing it. He insisted that we don't need to return a 1.5 MB JSON document in order to retrieve all the project licenses that are associated with a user. An array of uuids is enough.
I told him about a system that allows to you to specify which fields you want to return, and receive exactly that.
I will be pleased if this leads to a separate GraphQL API for our flagship project.
I keep my fingers crossed ;) GraphQL is really awesome!
PS: We have a tool making taking first steps with GraphQL easier (at least we hope so ;P).
It's GraphQL Editor (graphqleditor.com/) and it allows visualize your existing schema to get know with it better or create one from visual blocks. Maybe it will be helpful for you or your team if you will decide to jump into GraphQL train :)
Peace!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
My boss described GraphQL today without knowing it. He insisted that we don't need to return a 1.5 MB JSON document in order to retrieve all the project licenses that are associated with a user. An array of uuids is enough.
I told him about a system that allows to you to specify which fields you want to return, and receive exactly that.
I will be pleased if this leads to a separate GraphQL API for our flagship project.
I keep my fingers crossed ;) GraphQL is really awesome!
PS: We have a tool making taking first steps with GraphQL easier (at least we hope so ;P).
It's GraphQL Editor (graphqleditor.com/) and it allows visualize your existing schema to get know with it better or create one from visual blocks. Maybe it will be helpful for you or your team if you will decide to jump into GraphQL train :)
Peace!