Lenny’s Little Apollo Book

Written by Lenny Burdette in San Francisco. You can follow him on twitter but he doesn't tweet. Opinions written here do not necessarily reflect those of his employers and are subject to change.

Apollo Federation Patterns: Intro

An under-appreciated aspect of the GraphQL origin story is that Facebook.com is a monolithic application with a monolithic data store…

Apollo Federation Motivation

In a previous post , I listed some assumptions that motivate the desire for a solution like Apollo Federation: Microservices and the team…

Apollo Federation Patterns: Relationships

The quintessential use case for federation is modeling cross-service relationships. I highly recommend watching James' talk on Apollo…

Apollo Federation Patterns: Combining Data Sources

When Apollo released their federation libraries, this is the first pattern I tried. I was thrilled to discover that it worked exactly as I…

Apollo Federation Patterns: Managing Secrets

This is the first pattern of the series to leverage @requires directives and the advanced topic of "computed fields" . We try our best to…

Apollo Federation Patterns: Localization

Your schema may include enums or value types that aren't ideal for displaying in a UI. In this example, we have a PaymentStatus enum with…

Apollo Federation Patterns: Select * (Sorta)

By design, GraphQL does not provide a way to simply fetch all fields for a type without listing them out explicitly. However, you may want…

Apollo Federation Patterns: Polymorphic Relationships

By storing type names as well as IDs, you can model polymorphic relationships that cross any number of services. This post comes with a…