Looking for Guidance: GraphQL + Relational Backend for Next.js Project – Threads

Hey everyone! 👋
I’m building a project using Next.js and exploring different backend options. I want to set up a proper backend with GraphQL and support for two-way relational data (like foreign keys, joins between collections/tables, etc.).

Right now, I’m trying out Appwrite, but I’m not sure if it supports this type of setup — especially for:

Full GraphQL API support

Relational collections (e.g. Author ↔ Novels ↔ Chapters)

Efficient querying (e.g. getNovel → include related author + chapters)

My Questions:

Is it possible to implement this with Appwrite alone?

If not, what would you recommend? (e.g. Appwrite + Hasura, Supabase, or custom GraphQL server?)

Any tips or resources on how to model this kind of structure?

Appreciate any guidance or best practices 🙌

Thanks in advance!

TL;DR

Developers building Next.js project seeking guidance on setting up GraphQL with two-way relational data.

– Questioning if Appwrite supports full GraphQL API and efficient querying for relational collections like Author ↔ Novels ↔ Chapters.
– Asking if it’s feasible with Appwrite or if alternatives like Appwrite + Hasura, Supabase, or custom GraphQL server are better.
– Seeking tips/resources on structuring this data setup efficiently.