Latest articles, tutorials, and deep dives from ndlab tech blog.
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.
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.
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.
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.
GraphQL didn’t appear because REST failed. It appeared because many REST APIs were designed without client needs in mind.
Development hides problems. Production reveals them. This post shows how to reason about production builds, debug failures, and understand when build tooling actually matters.
Results