4 The Neo4j GraphQL Library

 

This chapter covers

  • Reviewing common issues that arise when building GraphQL API applications
  • Introducing database integrations for GraphQL that aim to address these common problems, including the Neo4j GraphQL library
  • Building a GraphQL endpoint backed by Neo4j, taking advantage of the features of the Neo4j GraphQL library such as generated Query and Mutation types, filtering, and temporal and spatial data types
  • Extending the functionality of our auto-generated GraphQL API with custom logic
  • Introspecting a GraphQL schema from an existing Neo4j database

GraphQL backend implementations commonly run into a set of issues that negatively impact performance and developer productivity. We’ve identified some of these problems previously (such as the "n+1 query problem") and in this chapter we take a deeper look at these common issues that arise and discuss how they can be mitigated using database integrations for GraphQL that make it easier to build efficient GraphQL APIs backed by databases.

4.1 Common GraphQL Problems

4.1.1 Poor Performance And The N+1 Query Problem

4.1.2 Boilerplate And Developer Productivity

4.2 Introducing GraphQL Database Integrations

4.3 The Neo4j GraphQL Library

4.3.1 Project Setup

4.3.2 Generated GraphQL Schema From Type Definitions

4.4 Basic GraphQL Queries

4.5 Ordering and Pagination

4.6 Nested Queries

4.7 Filtering

4.7.1 where Argument

4.7.2 Nested Filter

4.7.3 Logical Operators: AND, OR

4.7.4 Filtering In Selections

4.8 Working With Temporal Fields

4.8.1 Using A Date Type In Queries

4.8.2 Date and DateTime Filters

4.9.2 Distance Filter