The article explores multi-region database deployment options for a Slack-like corporate messenger. The data layer is designed to be highly available, scalable, and compliant with data residency requirements. Four multi-region deployment options are discussed: single stretched cluster, single geo-partitioned cluster, single cluster with read replicas, and multiple clusters with async xCluster replication. Each option has its trade-offs in terms of consistency, write latency, read latency, data loss on region outage, and complexity. The article demonstrates how to implement each option using YugabyteDB, a transactional distributed database for geo-distributed applications. The choice of deployment option depends on the specific requirements of each microservice.