Wrapping existing REST API in GraphQL (1,000,000 rubles methodology)
Is it possible to wrap the REST API in GraphQL? And how to make R&D for this technology? Usually, a test run of technology is usually done at TodoMVC. So let's do it.
Since Pavel is not a simple person we will have to take a complicated Todo application for example the Wrike project management system.
Let's take REST API from Wrike:
- 22 entity;
- 87 methods.
We will spend 160 hours on:
- 134 GraphQL types;
- 1002 fields and arguments;
- 51 explicit direct relationship between entity by id;
- 26 implicit feedbacks through filters.
Pavel will compress all the experience into an hourly talk. He will share his ideas, taken knocks, ideas, and thoughts on how to properly and efficiently wrap a REST API in GraphQL. Come and see it!
Before the talk you can look at what happened and what the speaker will talk about:
GraphQL rockstar, developer of Internet products, OSS maintainer. Since 2001 Pavel's main specialization is web technologies. He has extensive practical knowledge on backend/frontend development, administration, and architecture. Since the end of 2015, Pavel's main focus is on isomorphic applications. In summer 2016 he began the development of graphql-compose (GraphQL schema generator) in open source.
15 years of JS everywhere: from microcontrollers to rendering video in the cloud. More than 6 years of educational experience (at two universities and Illya's own courses), Ph.D. in Computer Science (field of interest: System Analysis and Theory of optimal decisions). Now works as front-end developer in GitLab.