# Data location constraints **URL:** \ **Category:** Using FoundationDB\ **Created:** [August 31, 2018, 1:39pm UTC](https://forums.foundationdb.org/t/data-location-constraints/674 "2018-08-31T13:39:32Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![ryanworl](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/ryanworl/32/440_2.png) [@ryanworl](https://forums.foundationdb.org/u/ryanworl)\ **Post date:** [August 31, 2018, 3:40pm UTC](https://forums.foundationdb.org/t/data-location-constraints/674/2 "2018-08-31T15:40:36Z")
I previously asked a similar question regarding data protection and this doesn’t appear to be on the roadmap. You would have to build this yourself using FoundationDB as a building block. > [@Multi DC replication](https://forums.foundationdb.org/t/multi-dc-replication/499): > > I see on the roadmap for 6.0 is multi-datacenter replication where a number of remote DCs can participate either synchronously or asynchronously in a cluster. I am asking because I also saw a goal is to provide the ability for clients to read from their local DC storage, which is related to a use case I’m interested in. Are there plans to allow certain data to be replicated globally and others to only be replicated within that region? Presenting an entirely flat keyspace globally and providin… --- _[View the full topic](https://forums.foundationdb.org/t/data-location-constraints/674)._