際際滷shows by User: bkaneweb / http://www.slideshare.net/images/logo.gif 際際滷shows by User: bkaneweb / Fri, 28 Apr 2017 16:17:39 GMT 際際滷Share feed for 際際滷shows by User: bkaneweb Declarative GraphQL: Adding GraphQL to our REST APIs without writing a single custom resolver /slideshow/declarative-graphql-adding-graphql-to-our-rest-apis-without-writing-a-single-custom-resolver/75507008 apollographqlmeetupslidesforupload-170428161739
Coursera has over 500 REST APIs in production. We're all in on GraphQL, but given this scale, it would be impossible to build a schema and write 500 custom resolvers to handle each of our endpoints. Instead, we used information we already had about our APIs (which actions are available, and request and response formats) to automatically build GraphQL resolvers and add them all to a single, unified schema. We also created a structured way for developers to define relations between models, in both forward and reverse directions, which will enable almost all pages on Coursera to be loaded via a single GraphQL query.]]>
Coursera has over 500 REST APIs in production. We're all in on GraphQL, but given this scale, it would be impossible to build a schema and write 500 custom resolvers to handle each of our endpoints. Instead, we used information we already had about our APIs (which actions are available, and request and response formats) to automatically build GraphQL resolvers and add them all to a single, unified schema. We also created a structured way for developers to define relations between models, in both forward and reverse directions, which will enable almost all pages on Coursera to be loaded via a single GraphQL query.]]> Fri, 28 Apr 2017 16:17:39 GMT /slideshow/declarative-graphql-adding-graphql-to-our-rest-apis-without-writing-a-single-custom-resolver/75507008 bkaneweb@slideshare.net(bkaneweb) Declarative GraphQL: Adding GraphQL to our REST APIs without writing a single custom resolver bkaneweb Coursera has over 500 REST APIs in production. We're all in on GraphQL, but given this scale, it would be impossible to build a schema and write 500 custom resolvers to handle each of our endpoints. Instead, we used information we already had about our APIs (which actions are available, and request and response formats) to automatically build GraphQL resolvers and add them all to a single, unified schema. We also created a structured way for developers to define relations between models, in both forward and reverse directions, which will enable almost all pages on Coursera to be loaded via a single GraphQL query. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/apollographqlmeetupslidesforupload-170428161739-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Coursera has over 500 REST APIs in production. We&#39;re all in on GraphQL, but given this scale, it would be impossible to build a schema and write 500 custom resolvers to handle each of our endpoints. Instead, we used information we already had about our APIs (which actions are available, and request and response formats) to automatically build GraphQL resolvers and add them all to a single, unified schema. We also created a structured way for developers to define relations between models, in both forward and reverse directions, which will enable almost all pages on Coursera to be loaded via a single GraphQL query.
Declarative GraphQL: Adding GraphQL to our REST APIs without writing a single custom resolver from Bryan Kane
]]> 765 5 https://cdn.slidesharecdn.com/ss_thumbnails/apollographqlmeetupslidesforupload-170428161739-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 https://cdn.slidesharecdn.com/profile-photo-bkaneweb-48x48.jpg?cb=1682060828 http://www.bkane.me