The Complete Strapi™ Course with Plugins and Deployment - The GraphQL Plugin and How It Works

The video tutorial explores the GraphQL API in Strapi, focusing on how to extend it similarly to the REST API. It explains the Strapi GraphQL plugin, based on Apollo Server and Nexus, and how to define schemas using JavaScript or TypeScript. The tutorial highlights the differences between GraphQL and REST APIs, such as having a single endpoint and using resolvers instead of controllers. It also covers implementing POST functionality in GraphQL and discusses the GraphQL flow, including types, resolvers, and middleware.

What is the foundation of the Strappy GraphQL plugin?

• Express and Sequelize

• Spring Boot and Hibernate

• Apollo Server and Nexus

• Django and Flask

How does a GraphQL API differ from a REST API in terms of endpoints?

• GraphQL uses a single endpoint, while REST uses multiple endpoints.

• Both GraphQL and REST use a single endpoint.

• GraphQL uses multiple endpoints, while REST uses a single endpoint.

• Both GraphQL and REST use multiple endpoints.

In GraphQL, what replaces controllers in handling requests?

• Resolvers

• Routers

• Middlewares

• Services

What are data models called in the GraphQL world?

• Types

• Entities

• Schemas

• Collections

What is the role of underlying services in GraphQL resolvers?

• To handle HTTP requests

• To define the GraphQL schema

• To manage user authentication

• To perform operations like fetching data