Building GraphQL Server
REST API was good for its time, as well as Swagger. But nowadays everybody talks about component approach, so in 2018 back-end developers should really take a look at GraphQL. In fact, it's a new standard of super comfortable API for front-end developers and their component approach. But front-end developers' meat could become poison for unprepared back-end developers.
In this talk we'll discuss things that back-end developers should pay attention to. Which parts GraphQL Server consists of — there are lots of packages in the internet, so it would be good to know what we should install and, more importantly, why. What is schema and how to write it for the whole thing to work. We'll talk about authorization, about how to write a simple ACL. We'll address the issues of performance and safety. We'll delve into file loading, schema generation, documentation, and see if all is good with the API versioning.
This talk will be useful for junior, middle and senior developers alike, whether you are already using GraphQL or just sizing up this promising technology.
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.