Working with GraphQL as a source of truth

I often reminisce about the days without GraphQL with an ironic smile on my face. I remember how, as a frontend developer, I had to call backend developers and ask why a certain field suddenly disappeared or what the name of an endpoint was because I couldn’t remember it anymore. Of course, even in REST, there are specification systems that allow for a detailed description of our backend; however, they don’t enforce it on the backend developer – they only enable it.

I was already interested in the concept of a single source of truth even before GraphQL, but as soon as I understood the power of GraphQL, I immediately decided to teach it to everyone in our company and turn it into a competitive advantage.

Understanding the source of truth

Let’s imagine a scenario where we’re starting a project from scratch without any existing systems in place. Typically, the process involves creating wireframes and...