We bought into the GraphQL vision on past projects but I came out the other end never wanting to work with it again. So much effort is put into trying to make "

We bought into the GraphQL vision on past projects but I came out the other end never wanting to work with it again. So much effort is put into trying to make "one API to rule them all". The shape of that API will always have inefficiencies, waste, and misaligned expectations about the data. If you control the client the server then most likely your client has a function wanting data so just call a function on the server to provide it. A generic http-based abstraction in the middle isn't always the right answer. Our most recent project is a SPA making RPC calls with a BFF* architecture. We couldn't be happier. * https://samnewman.io/patterns/architectural/bff/ https://samnewman.io/patterns/architectural/bff/