Schema-first development with GraphQL
GraphQL improves both your API's performance and the performance of your team in general. Schema-first GraphQL development forces front- and backend teams to agree on a strict contract up front, enabling them to work quickly and efficiently while staying on spec. Danielle Man discusses the benefits of schema-driven development and shares lessons learned using GraphQL in production.
| Talk Title | Schema-first development with GraphQL |
| Speakers | Danielle Man (Meteor Development Group) |
| Conference | O’Reilly Fluent Conference |
| Conf Tag | The Web Platform in Practice |
| Location | San Jose, California |
| Date | June 20-22, 2017 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
GraphQL improves both your API’s performance and the performance of your team in general. Schema-first GraphQL development forces front- and backend teams to agree on a strict contract up front, enabling them to work quickly and efficiently while staying on spec. Danielle Man discusses the benefits of schema-driven development and shares lessons learned using GraphQL in production, building open source tools for the GraphQL community, and going from zero to GraphQL with two production applications. This efficiency is enabled by great tools in the GraphQL ecosystem like GraphQL clients, data mocking systems, and GraphQL developer tools. If you design your schema up front, your backend teams have a strong spec to develop to and your frontend teams can start building components immediately. Danielle shares how her team was able to build a production app in less than three months using this approach.
