# Multi-region setup with write and read clusters

**URL:** <https://forums.foundationdb.org/t/multi-region-setup-with-write-and-read-clusters/3633>\
**Category:** Using FoundationDB\
**Created:** [November 2, 2022, 4:27pm UTC](https://forums.foundationdb.org/t/multi-region-setup-with-write-and-read-clusters/3633 "2022-11-02T16:27:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jcampii](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/jcampii/32/1455_2.png) [@jcampii](https://forums.foundationdb.org/u/jcampii)\
**Post date:** [November 2, 2022, 4:27pm UTC](https://forums.foundationdb.org/t/multi-region-setup-with-write-and-read-clusters/3633/1 "2022-11-02T16:27:56Z")

</div>

I’m interested in using FoundationDB as a highly available event store. I plan on using the multi-region setup. I understand that the reads of a client can also go to the warm secondary region, not only the hot primary region. I am fine with having some time lag so that I would use the cache to avoid version checks.

We want to have a setup with Kubernetes clusters that are distributed worldwide - most of them as read-only clusters and some of them as write clusters.

Is there a setup of FoundationDB that would make it possible with multiple locations? So far I would say no (or not really), also looking at this old topic [Best configuration for worldwide low latency with small databases](https://forums.foundationdb.org/t/best-configuration-for-worldwide-low-latency-with-small-databases/2451)