How does Supabase mesh with backends?
Hiya
While I'm using Supabase with success for small and easy things, in the long term I want to involve it in more advanced features.
For example I'd like to have a backend that will perform a couple of database operations on behalf of a user, collate and transform the results, and return that. I get the feeling that Supabase was designed to be called from frontend and mobile programs and I should approach this differently, but I don't really know how.
I thought I would just make requests to my backend with the logged in user's JWT, and use that to authenticate requests to Supabase, but it's hard to pull off. Is this something idiomatic or should I just use postgres-side logic and edge functions for more complicated logic? Are there any examples of using Supabase with backends?
While I'm using Supabase with success for small and easy things, in the long term I want to involve it in more advanced features.
For example I'd like to have a backend that will perform a couple of database operations on behalf of a user, collate and transform the results, and return that. I get the feeling that Supabase was designed to be called from frontend and mobile programs and I should approach this differently, but I don't really know how.
I thought I would just make requests to my backend with the logged in user's JWT, and use that to authenticate requests to Supabase, but it's hard to pull off. Is this something idiomatic or should I just use postgres-side logic and edge functions for more complicated logic? Are there any examples of using Supabase with backends?
