You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 24, 2024. It is now read-only.
Kafka and Connectors will provide GraphQL API along with the REST.
While rest is the main choice for APP interface we could build and utilize GraphQL API.
Research here is needed how to expose GraphQL API for Quarkus/Java
More options for the user. If you have lots of relations in your resources, GraphQL can make it easier to get a set of related data in one request (which would require multiple REST api calls). It's also typically easier to use for some front end developers due to how easy it is to introspect / explore.
The go lib we are using for the connectors automatically implements the graphlq endpoint using the openapi spec, so it's super easy to maintain. It translates the graphql requests it receives and makes REST api calls. It can be used as side car to enable graphql on a normal REST sever that has a well defined openapi spec.
Kafka and Connectors will provide GraphQL API along with the REST.
While rest is the main choice for APP interface we could build and utilize GraphQL API.
Research here is needed how to expose GraphQL API for Quarkus/Java
FYI @chirino
The text was updated successfully, but these errors were encountered: