Managing Multi-Region User Data Without Duplicating Database Logic

Hey fellow developers! I'm delving into the complexities of handling multi-region user data in production environments. For instance, how do we deal with the following setups? EU users are directed to an EU database to handle GDPR and latency concerns, US users go to a US database, and Asian users have their own regional database. The challenge arises with tools like Supabase and Neon, which force you to select a single region for your database. How does this work for a global user base? What are your strategies for this?

Here are a few options I'm considering: 1) Running multiple databases and manually routing users, 2) centralizing everything in one region and accepting the trade-offs of latency and compliance, 3) utilizing replicas or edge caching (this suggestion came from AI), or 4) perhaps another approach?

If you're using multiple databases, how do you manage the routing logic? Is it centralized or scattered across different services? I'm eager to hear about real-world practices versus what tools suggest!