Handling name collisions in GraphQL schema stitching

GraphQL Schema Stitching is the mechanism of composing multiple GraphQL schemas together into a single unified schema. This plays strongly into the concept of “back-ends for front-ends” which is building a specialised API designed specifically for the app in question. This “API Gateway” takes the schemas of the micro-services needed for it’s functionality, combines, extends and exposes them to the front end.

My git aliases

I’ve seen a few posts around lately with people discussing how they work with git during day to day development and I thought I’d share mine.

Guarding against N+1 issues in GraphQL

The N+1 query problem is a common one to encounter during software development, particularly with ORMs (Object Relational Mappers) and their capabilities around lazy loading. A quick example looks like

Exporting a GraphQL Schema

I’ve been playing around with GraphQL at work quite a bit lately and starting to put together some thoughts on how it can fit into your application (and more importantly where it doesn’t).

EF Core Client Side evaluation (and how to stop it)

EF Core has a feature that supports parts of a query being evaluated on the server and parts on the client, the decision is driven by the whether the underlying LINQ provider can convert the expression into SQL.