Data-First GraphQL

There is a debate in the GraphQL community between "schema-first" and "code-first" development. Yet, there is a third way: data-first GraphQL APIs. This is where principles and pragmatism meet. "Do not Repeat Yourself", "Domain-Driven Design," and "Data-Driven Development" are important principles in software. Just as important are pragmatic concerns like integrating vast reservoirs of heterogeneous brownfield data sources, exposing it all as production-grade APIs, and doing it fast. The remorseless logic of these factors leads ineluctably to one conclusion: APIs must derive from the data, not from a schema or from code that has been curated manually, independent of the data. In this talk, we at Hasura wade into the debate to argue for this third way. Ship APIs faster, cheaper, and more reliably with data-first GraphQL development.
Speaker Name
David A. Ventimiglia
Speaker Bio
My name is David A. Ventimiglia, and I am a Solutions Architect at Hasura. I have been a theoretical astrophysicist, a software engineer, a data engineer, and a machine learning engineer. I love writing code, and yet I believe code is better when there's less of it. Now, I work at Hasura where I show customers how much can be accomplished with how little code.