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:

• Live GraphQL proxy;
• The relationship diagram of the real "hairy" GraphQL;
• Code repository.