Migrating from REST to GraphQL (2018)
1h 3mAdvanced2018-11-15
Authors

Emmanuel Henri
Executive with 20+ years of experience in programming and design
Course details
Why use GraphQL over REST APIs? GraphQL is better at querying multiple databases, offers an easy-to-learn syntax, and allows you to retrieve only the data you need. Learn when you should migrate from REST to GraphQL, and how to convert your REST API add, update, and delete operations into GraphQL mutations. Instructor Emmanuel Henri also explains how to build simple, useful queries; use arguments, fragments, and aliases in queries; and perform operations using GraphQL.
Learning objectives
Setting up GraphQL
Creating the initial schema and type
Setting up simple queries
Leveraging arguments and aliases
Reading, updating, adding, and deleting items with GraphQL
Posting data with mutations
Learning objectives
Setting up GraphQL
Creating the initial schema and type
Setting up simple queries
Leveraging arguments and aliases
Reading, updating, adding, and deleting items with GraphQL
Posting data with mutations
Skills covered
RESTGraphQLMigratingProgramming LanguagesOpen SourceSoftware Development
Concepts
0. Introduction
- 01 - Replace REST with GraphQL
- 02 - What you should know
1. First Steps
- 03 - Why use GraphQL for REST
- 04 - REST project introduction
- 05 - Setting up GraphQL
- 06 - Setting up the database
- 07 - GraphQL refresher
2. Add Items with GraphQL
- 08 - Creating the initial schema and type, part 1
- 09 - Creating the initial schema and type, part 2
- 10 - Setting up the initial resolvers
- 11 - Finalizing the DB connection
- 12 - Adding a few items with GraphiQL
3. Read Items with GraphQL
- 13 - Simple queries in GraphQL
- 14 - Leveraging arguments in queries
- 15 - What are aliases and usage
- 16 - Fragments basics
4. Update Items with GraphQL
- 17 - Overview of mutations
- 18 - Coding your update mutation
- 19 - Testing your update mutation
5. Delete Items with GraphQL
- 20 - Coding your delete mutation
- 21 - Final test for your mutation
Conclusion
- 22 - Next steps