You're reading from GraphQL Best Practices Gain hands-on experience with schema design, security, and error handling

Product type Paperback

Published in Oct 2024

Publisher Packt

ISBN-13 9781835467145

Length 422 pages

Edition 1st Edition

Languages

JavaScript

Tools

GraphQL

Concepts

Web Programming

Author (1):

Artur Czemiel

View More author details

Table of Contents (23) Chapters

Preface

1. Part 1 - Why GraphQL?

2. Chapter 1: Unveiling the Holy Grail of Communication – GraphQL FREE CHAPTER

3. Chapter 2: Applying an AI-Friendly Approach to GraphQL

4. Part 2 - Schema-First Design Patterns

5. Chapter 3: Crafting Effective GraphQL Schemas

6. Chapter 4: Building Pipes

7. Part 3 - Exploring Possible Ways to Use GraphQL

8. Chapter 5: Transitioning from REST to GraphQL

9. Chapter 6: Defining GraphQL Transformers

10. Chapter 7: Understanding GraphQL Federation

11. Part 4 - Advanced GraphQL

12. Chapter 8: Executing Schema-First Systems

13. Chapter 9: Working on the Frontend with GraphQL

14. Chapter 10: Keeping Data Secure

15. Chapter 11: Describing Errors in GraphQL

16. Chapter 12: Documenting your Schema

17. Chapter 13: Tackling Schemas with Visualization

18. Part 5 - From an Idea to a Working Project

19. Chapter 14: From an Idea to a Working Project – Backend Development with GraphQL and TypeScript

20. Chapter 15: From an Idea to a Working Project – Frontend Integration with GraphQL and TypeScript

21. Index

Why subscribe?

22. Other Books You May Enjoy

Understanding the GraphQL query language

As I mentioned earlier, introspection is vital, and now I present to you the most important part that benefits from introspection: the GraphQL query language. While REST APIs allow for exposing the JSON schema, which provides information about the API structure, I have rarely encountered good use cases for it throughout my professional career. On the other hand, the GraphQL query language is widely used in a proper manner because the language makes it hard to make mistakes.

When I first started using GraphQL, I had this feeling of “Why didn’t people agree on such a standard earlier?” We didn’t need artificial intelligence or quantum computers for it – all we needed was to communicate and reach a consensus – but now GraphQL is commonly used and it is a standard we needed. While it may not be visibly apparent at this moment, I can confidently say that GraphQL is pushing programming technologies forward...