Decoupling Frontends and Backends with GraphQL

The needs of the frontend and the needs of the backend don’t always coincide, leading to a lot of extra code to make an API meet the needs of the frontend (e.g. the backend for frontend pattern). Anant Jhingran will explore whether GraphQL can bridge the divide between the backend and frontend developers by meeting the needs of both.

Decoupling Frontends and Backends with GraphQL

The backend developer creates APIs that reflect how they see the data. In many cases, this does not meet the needs of the frontend developer who needs data from APIs in the context of the apps they are building. The backend-for-frontend pattern grew out of this need to support multiple user interfaces with differing needs, particularly mobile interfaces. This decoupling of the frontend and backend is a good thing. It frees frontend developers from having to wait on changes to an underlying API to iterate on the UI but it can lead to a significant amount of code to bridge the divide.

In this session, we’ll see how using GraphQL as the frontend API can simplify this decoupling by eliminating the need for code to make the API meet the needs of the frontend. In particular, how things like interfaces, routing, and declarative specifications in GraphQL can make decoupling much easier and accelerate application development.

Anant is the founder and CEO of StepZen — a startup with a new approach for simplifying how developers access the data they need to power digital experiences. With a career that spans IBM Fellow, CTO of IBM’s Information Management Division, CTO of Apigee, and product leader at Google Cloud, Anant has spent his career at the forefront of innovation in databases, machine learning, and APIs. At StepZen, Anant is enjoying creating a company that brings his love of these technologies together to simplify, accelerate and scale front-end development.

More Awesome Sessions