require a two step process (Add new functionality to the right schema, extend at gateway to allow for relationships) • We end up with something still quite centralized because of where the relationships are formed and the final schema is built • It's not very clear where new schema use cases go. We risk that a lot of domain logic will leak into the gateway, making our GraphQL gateway a monolithic API, the thing we wanted to avoid in the first place using this solution.