Upcoming Change: Improved Experimental Routing for Read Replica Load Balancers #34494
jose-ledesma
announced in
Changelog
Replies: 1 comment 1 reply
-
|
Super excited about this! One quick question though: in https://supabase.com/docs/guides/platform/read-replicas#experimental-routing is says that requests using custom domains won't be routed through the load balancer. Does that mean we can't use the geo-aware read replicas if we also want custom domains (to get our domain into Sign in with Google etc)? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Starting on April 4th, 2025, we will be enhancing the routing behavior for experimental routing on eligible Data API requests. This change affects GET requests to Data APIs only; the routing behavior for all other requests remains unchanged:
Current behavior: Round-robin distribution among all databases (primary and all read replicas) in your project
New behavior: Geo-routing that directs requests to the closest available database
This enhancement delivers a better experience for your users by minimizing latency to your project. You can maximize these benefits by strategically placing Read Replicas close to your major customer locations.
For more information on geo-routing and experimental routing, please visit our documentation
Beta Was this translation helpful? Give feedback.
All reactions