Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API Protocol: GraphQL(Hasura) vs. RESTful #4

Open
hubts opened this issue Jun 14, 2024 · 0 comments
Open

API Protocol: GraphQL(Hasura) vs. RESTful #4

hubts opened this issue Jun 14, 2024 · 0 comments

Comments

@hubts
Copy link
Owner

hubts commented Jun 14, 2024

📸 What is this issue?

What is an issue? Please explain with some screenshots.

  • If we use Hasura as GraphQL server, client will be connected to it. Hasura server offers autonomous query, but we should manage Hasura metadata. Furthermore, we should check response DTO to import in Swagger and Hasura actions.
  • If we implement RESTful API, client will be connected to the server directly with Swagger document generated. REST server does not need to manage other points, but all features must be implemented and some response DTO should be generated concisely.
  • Now which should we select the protocol between GraphQL vs. RESTful?

✨ Expected Results

What result do you expect?

  • Branch main implemented to use GraphQL with Hasura.
  • Branch rest-api implemented to use RESTful without Hasura. In this case, Hasura is just used like PGAdmin (DB Administrator).
  • We should select the protocol between them.
  • However, when we use RESTful server protocol, some features can be used as Hasura actions if we consider it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant