Apollo GraphOS router

[ryscheng]

What is it?

Hasura is compatible with Apollo federation
https://hasura.io/docs/3.0/graphql-api/apollo-federation/

We can set this up, since we're starting to use more Apollo server features in the frontend

[ryscheng]

Looks like Supabase isn't about that Apollo federation life yet
supabase/pg_graphql#374

FWIW, Hasura is
https://hasura.io/docs/3.0/graphql-api/apollo-federation/

If Supabase supported it, then there might be an interesting argument to have Apollo GraphOS router directly route between Supabase, Hasura, and our Next.js API, merging entities between the 3 (e.g. User entities). But tbh, this seems like an over-optimization atm. It's also less useful in a world where we might want Dagster/dbt to apply transformations on Supabase data, so we probably need to connect it directly to the data backend anyway.

So in the spirit of not over-engineering, let's close this out for now, keeping with the existing architecture, where the client will directly talk to separate backends to compose functionality
Client => Hasura GraphQL API (to fetch metrics and project data)
Client => Supabase (to CRUD application state)
Client => Next.js server, which can directly talk to Clickhouse/Supabase if need be