There are several design patterns depending on whether you need to optimize the latency for reads, writes, or both.

If it's all abour reads, then you can use follower reads (as shown in the article) or read replicas. If you also need writes, then a geo-partitioned deployment or standalone database instances for each region would be good starting points.