GraphQL: how to make clients enjoy using your API
Seemingly long gone are times where one monolith application on server was responsible for handling all the data. Likewise, nowaday releasing just web application without mobile counterpart does not seem like a good idea from business perspective - and those several client applications, although doing roughly the same thing, may have different business requirements. Couple that with separation of concerns on the server side, and a big headache is inevitable.
During this talk, I will go through one, relatively new solution to above issues - GraphQL. Coming from Facebook, it makes working with the API a really pleasant experience for the clients, as communication with server is declarative, not imperative. It also helps keep things in check on the server's side by providing a schema language. We will cover basic concepts, see how querying looks like from client's side (and why it is so good), as well as look at example implementations for pure Python, Django and SQLAlchemy.
Tomasz is a programmer by heart who started messing with web development when his age was composed of only single digit. For the past four years, he has worked as a Python/JS developer in the biggest European Python software house, STX Next, that focuses on the best practices regarding Python, as well as development and agile processes.
He gets thrills when he sees clean and well-written code. He also promotes explicitness and separation of concerns wherever he can - that's why Python is his choice as the most favourite language.