Skip to content
This repository has been archived by the owner on May 29, 2024. It is now read-only.

Evaluate the cost of having GraphQL to query the catalog #761

Open
ia3andy opened this issue May 15, 2019 · 2 comments
Open

Evaluate the cost of having GraphQL to query the catalog #761

ia3andy opened this issue May 15, 2019 · 2 comments

Comments

@ia3andy
Copy link
Contributor

ia3andy commented May 15, 2019

From what I observed at the RivieraDev GraphQL workshop:

  • it would remove most of the need to have a client library
  • it would give a way to provide a client in nearly any language that handle GraphQL
  • it auto adds “api” validation for request in the frontend and in the backend

And it’s actually quite easy to put in place.

Since we are migrating the creator, maybe now is the time?

@edewit
Copy link
Member

edewit commented May 15, 2019

love that idea, would make it easy to query and we don't have to maintain this translation between what is needed in the frontend and the model that is used in the backend

@wtrocki
Copy link

wtrocki commented Sep 5, 2019

@ia3andy @edewit we are working on launcher booster that will support graphql.
We are hoping to use project called https://graphback.dev that is maintained by Red Hat AeroGear community. We support generating backend and frontend from GraphQL schema.

This can be also used for internal needs

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants