장점
단점
장점
단점
출처:
https://velog.io/@zoeyul/Graphql-code-first-vs-schema-first
https://velog.io/@ko1586/Schema-first-vs-Code-first
https://veritasgarage.tistory.com/177
https://velog.io/@uiop5487/Schema-first-vs-Code-first
(영문 해석)
When creating a GraphQL server there are two artifacts required by the GraphQL engine: a schema, which defines all the types and fields, and the resolvers, which are the collection of functions that are called to return the data for those types.
This pattern is popular in languages that do not have a type system, like JavaScript, because the GraphQL engine is providing this API type-safety for us. It is also the pattern used by many popular GraphQL servers, like apollo-server, which adds to the exposure of the pattern, as new GraphQL developers will likely see this pattern first when learning GraphQL for the first time.
This is more common in type-safe languages, such as graphql-kotlin, where you can run reflections against source code, however, it can be used by any GraphQL server language.
Source:
https://blog.graphqleditor.com/graphql-schemafirst-codefirst
https://blog.logrocket.com/code-first-vs-schema-first-development-graphql/
https://www.apollographql.com/blog/backend/architecture/schema-first-vs-code-only-graphql/