Edge Databases

[fredguest]

Feature request

Is your feature request related to a problem? Please describe.

For apps that are distributed "at the edge", using Cloudflare Pages or Vercel for example, having a database instance that is tied to a single geographic location can result in slower response times than if the apps were also served from the same single geographic location as the database.

For more details see the tests conducted here:
https://www.youtube.com/watch?v=yOP5-3_WFus

Describe the solution you'd like

Automagic globally distributed database instances.

Additional context

@kiwicopple has discussed this idea on Reddit but it seemed worth having a feature request to track here.

https://www.reddit.com/r/Supabase/comments/s9rdfd/globally_distributed_postgres_with_supabase

ceo here. Yes, we're looking at this. First we need to make all the middleware multi-tenant. We have already done this for the storage server and pg-meta, we're working on PostgREST, and Realtime now. Auth is going to be the tricky one, so we'll tackle that after we support SAML. FYI - multi-tenant: one instance works with multiple databases. This is also important for costs and database branching.

[fredguest]

In the mean time, this kind of thing is a good solution:

"Cache Supabase data at the Edge with Cloudflare Workers and KV Storage"
https://egghead.io/courses/cache-supabase-data-at-the-edge-with-cloudflare-workers-and-kv-storage-883c7959