API/Schema first support? #1462
-
|
Hello, Our team embraces API/Schema first development approach. We come up with GraphQL schemas first, and use codegen tools for the following development. Our early feasibility study of Does anyone have any recommendation / thoughts regarding API/Schema first approach with Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
It's not smallrye-graphql that gives to a transitioning to Java Native, but rather Quarkus, that use smallrye-graphql. You can still use a code first approach in Quarkus. Create your schema and generate the relevant code. Include this in a Quarkus App, and then include the vert-graphql extension, that will pull in graphql-java. SmallRye GraphQL is a code first library. It generates the Schema and gives you an easy way to create endpoints. There is not much value to add when you provide the schema and generate the code. |
Beta Was this translation helpful? Give feedback.
It's not smallrye-graphql that gives to a transitioning to Java Native, but rather Quarkus, that use smallrye-graphql. You can still use a code first approach in Quarkus. Create your schema and generate the relevant code. Include this in a Quarkus App, and then include the vert-graphql extension, that will pull in graphql-java. SmallRye GraphQL is a code first library. It generates the Schema and gives you an easy way to create endpoints. There is not much value to add when you provide the schema and generate the code.