Roy Derks

Wrap existing REST APIs into one single GraphQL endpoint on both the client and server side.

Your frontend developers are pushing to get started with GraphQL, but you don’t have the backend capacity to migrate your existing REST APIs to GraphQL? Or you want to have a GraphQL API next to your existing endpoints that are based on REST, without having to rewrite all your controllers? 

In this talk I’ll show how to wrap existing REST APIs into one single GraphQL endpoint on both the client and server side. This allows you to access the power of GraphQL without having to change any of your existing code or connect to a database.

2020

Frontend Developer Love

GraphQL Without a Database

Boilerplates are often used to kickstart the development process of new apps. But, this leads to a lot of copied code that isn't needed for most projects.

Boilerplates are often used to kickstart the development process of a JavaScript application. However, this leads to a lot of copied code that isn't needed for most projects, while developers aren't exactly knowing what they are doing.

2018

dotJS

Boilerplates Are The New Copy-Paste

Why GraphQL will become the new standard for accessing external data in your React Native app. I will show how using GraphQL instead of REST services the development process becomes even more declarative as GraphQL will take away the (imperative) hassle of tying data from multiple endpoints together. This will increase the level of complexity in React Native development, while also increasing the performance of the application.

Slides: https://www.slideshare.net/RoyDerks1/graphql-will-do-to-rest-what-json-did-to-xml-113763718