Why GraphQL exists - Quick Recap

Recall & Review

beginner

What problem does GraphQL solve compared to traditional REST APIs?

GraphQL solves the problem of over-fetching and under-fetching data by allowing clients to request exactly what they need in a single query.

beginner

How does GraphQL improve efficiency in data retrieval?

GraphQL lets clients specify the exact fields they want, reducing unnecessary data transfer and multiple requests.

intermediate

Why is flexibility important in GraphQL's design?

Flexibility allows clients to evolve their data needs without changing the backend, making development faster and easier.

intermediate

What is a common limitation of REST APIs that GraphQL addresses?

REST APIs often require multiple endpoints and requests to gather related data, while GraphQL can fetch all related data in one query.

intermediate

How does GraphQL help frontend and backend teams work better together?

GraphQL creates a clear contract where frontend can ask for data independently, reducing backend changes and speeding up development.

What is a main reason GraphQL was created?

A To make APIs slower but more secure

B To replace databases entirely

C To allow clients to request only the data they need

D To remove the need for servers

GraphQL was created to let clients specify exactly what data they want, avoiding over-fetching or under-fetching.

How does GraphQL reduce the number of requests compared to REST?

A By limiting data to only one field

B By caching all data on the client

C By using multiple endpoints for each data type

D By combining multiple data requests into a single query

GraphQL allows clients to request all needed data in one query, reducing multiple round trips.

Which of these is NOT a benefit of GraphQL?

A Automatic database indexing

B Flexible queries

C Single endpoint for all queries

D Exact data fetching

GraphQL does not handle database indexing; it focuses on flexible data querying.

Why might frontend developers prefer GraphQL?

A They can get exactly the data they want without backend changes

B They don't need to write any queries

C GraphQL automatically generates UI components

D It requires no knowledge of data structure

GraphQL lets frontend developers request data precisely, reducing dependency on backend changes.

What is a key difference between REST and GraphQL?

A REST is only for mobile apps; GraphQL is for web apps

B REST uses multiple endpoints; GraphQL uses a single endpoint

C REST requires no server; GraphQL requires no client

D REST is a database; GraphQL is a programming language

REST APIs typically have many endpoints, while GraphQL uses one endpoint for all queries.

Explain in simple terms why GraphQL was created and what problems it solves.

Think about how apps get data and what can be annoying about old ways.

Describe how GraphQL helps frontend and backend teams work more smoothly together.

Focus on teamwork and communication between developers.