2
Price inter-connectivity between supabase functions differently
Source: supabase/supabase#28403 · opened by @alita-moore
I am using supabase functions as my defacto server, and for services to communicate with each other they make network requests to the other functions in a standard fashion. This has been working great for me and is really clean imo. However I have a few concerns: 1. it's very slow 2. it's expensive These aren't deal breakers for me yet because I don't have a lot of traffic and am okay with moderate latency. Further, I can self-host when I'm ready / needing a speed increase and budget cut. With that said, it would be super helpful if inter-function communications were treated differently from regular function calls (e.g. from the client). Both in terms of how long they take and how expensive it is. For example, perhaps inter-communication could be priced at $0.2 / million rather than $2/million. Because a single client request can end up making many calls to other functions / services. Also, I'm a bit surprised by how slow the inter-function re…
No pledges yet. Be the first to back this.
Comments
Similar requests
Edge functions not showing in local Supabase Studio
15 votes · 0 comments
Add option to `supabase functions deploy` to delete non-local functions
2 votes · 0 comments
Replace Deno Runtime for Edge Functions with Dapr
11 votes · 0 comments
NestJS Support in Supabase Edge Functions
17 votes · 0 comments
Improving the functionality of Edge Functions
3 votes · 0 comments
No comments yet.