Skip to content
NDLab Blog
Sign in
Part 8 — GraphQL with NestJS: Schemas, Resolvers, Clients
Completed 6 episodes ~ 18 min total read

Part 8 — GraphQL with NestJS: Schemas, Resolvers, Clients

Start series
Share Episodes About

Episodes

6 items • ~18 min
  1. 1

    Part 8.1 — Why GraphQL Exists: Problems It Tries to Solve

    Updated

    GraphQL didn’t appear because REST failed. It appeared because many REST APIs were designed without client needs in mind.

    Published Feb 5, 2026 • 3 min read
  2. 2

    Part 8.2 — GraphQL Mental Model: Schemas, Types & Resolvers (Conceptual)

    Updated

    You don’t need GraphQL to benefit from GraphQL thinking. This post explains schemas, types, and resolvers—and how they map directly to clean REST architecture.

    Published Feb 6, 2026 • 3 min read
  3. 3

    Part 8.3 — Designing REST APIs That Feel Like GraphQL

    Updated

    You don’t need GraphQL to give clients control. This post shows how to design REST APIs that feel flexible, intentional, and predictable—without sacrificing debuggability or caching.

    Published Feb 7, 2026 • 3 min read
  4. 4

    Part 8.4 — Client-Driven Data with REST: Avoiding Over-Fetching

    Updated

    Over-fetching is a client problem as much as a server problem. This post shows how React apps can drive data needs intentionally—without turning REST APIs into guesswork.

    Published Feb 8, 2026 • 3 min read
  5. 5

    Part 8.5 — Backend Architecture: Controllers vs “Resolvers” in NestJS

    Updated

    If you squint a little, a NestJS controller method already is a resolver. This post shows how to embrace that idea without introducing GraphQL complexity.

    Published Feb 9, 2026 • 3 min read
  6. 6

    Part 8.6 — When (and When Not) to Use GraphQL in Real Systems

    Updated

    GraphQL is powerful—but expensive. This post helps you decide, based on real constraints, whether GraphQL is worth adopting or whether REST will serve you better.

    Published Feb 10, 2026 • 3 min read