Session

Transition from REST API to GraphQL using real projects as an example

Dreaming of unloading Backend developers as much as possible, I decided to try to delegate the logic of grouping data in server requests to Frontend developers. GraphQL was chosen as the final solution. First, we made a couple of test projects on it and, after the checks, we started using GraphQL in customer projects. A lot of water under the bridge and knowledge about the features of the translation which could be shared has accumulated. In the process of transition, we encountered many features of this technology and the experience gained, at the moment, allows us to reveal the following points:

* Pros and Cons of Switching to GraphQL
* How to gradually switch to GraphQL
* How to safely delegate data assembly logic to Frontend
* How you can get the maximum effect from connecting GraphQL to a project with microservices
* The disadvantages of technology that we realized only when we had faced with them
* What you need to know in order not to shoot yourself in the foot while connecting GraphQL

Anton Morev

Wormsoft, CTO

Moscow, Russia

Actions

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top