Designing GraphQL Schemas: Avoid the downsides of GraphQL's flexibility - Nik Graf

Find the latest React.js talks & workshops at https://portal.gitnation.org
 
  🗓

Talk recording from React Advanced 2019 Conference  

Check out the latest React Advanced London news – https://reactadvanced.com

See other React conferences by GitNation
React Day Berlin – https://reactday.berlin
React Summit Amsterdam – https://reactsummit.com/

Designing GraphQL Schemas

GraphQL brings joy to using APIs. Even though it's based on a type system, GraphQL in many ways is more flexible than REST. But the flexibility that makes GraphQL a joy to work with can have its downsides if you aren't careful.

Schema design is an area where one small oversight at the beginning can get you stuck having to deal with weird naming, bloated duplicates, and other annoying workarounds. It doesn't have to be like this!

Nik Graf has extensive experience designing GraphQL schemas, for a variety of business applications.Nik has prepared several examples following different design patterns. Through exploration and comparison, you'll come away with actionable knowledge for designing and extending schemas.

 
Subscribe to our channel to see more React (Native) talks:    / @reactconferences