There are two different approaches to GraphQL development.
1- schema-first development.
2- code-first development. #graphql
With schema-first development, you manually define your API’s schema using the GraphQL Schema Language. The code in your service only implements this schema.
With code-first development, you don’t have a schema file. Instead, the schema gets generated at runtime based on definitions in code.
Schema first approach will lead to better , scalable and human readable API as well as good frontend developer experience. However a lot of initial collaborations between teams will be required.
It might be marginally quicker to generate schema from the code and the backend code structure will be in focus for good integration.
I am curious to know What else could be a factor for pro/con of schema first and code first development approach ? #graphql
• • •
Missing some Tweet in this thread? You can try to
force a refresh
If you work with #GraphQL and are CURIOUS on what the recently open source released Domain Graph Service framework by @NetflixEng is ? I have attempted a really short summary of the same below 🧵👇
#Annotation-Based : The framework’s core revolves around the annotation-based programming model familiar to Spring Boot developers. Just start the Spring Boot application, the /graphql endpoint along with the query editor on /graphiql endpoint will be available.
#Java / #Kotlin : So you can say it is primarily ofadvantage for Java developers. Regardless of whether you use Java or Kotlin, the DGS framework provides an easy way to build GraphQL services in Spring Boot.