Is maintaining a GraphQL API worth it?
Hey all-
The answer to this question will be obvious to some of you, but here it goes: if the Supabase JS SDK + RLS policies are so powerful, what's the point in having a dedicated GraphQL API server?
It seems rather redundant to have a dedicated server when you can accomplish any data operation with the SDK. The only reason I can think of is that it might be easier to cache GraphQL API responses than straight database responses.
Is there any other reason to maintain a GraphQL API that I'm not thinking of? For context, I have a small app that runs mobile only (maybe web in the future). Thanks
The answer to this question will be obvious to some of you, but here it goes: if the Supabase JS SDK + RLS policies are so powerful, what's the point in having a dedicated GraphQL API server?
It seems rather redundant to have a dedicated server when you can accomplish any data operation with the SDK. The only reason I can think of is that it might be easier to cache GraphQL API responses than straight database responses.
Is there any other reason to maintain a GraphQL API that I'm not thinking of? For context, I have a small app that runs mobile only (maybe web in the future). Thanks
