PRO+ Premium Content/Access

Thank you for joining!
Access your Pro+ Content below.
June 2017, Vol. 1, No. 4

Understand the principles of data residency

There is a general principle that systems architects need to keep applications and data colocated. With on-premises end-user computing deployments involving multiple sites, that often results in remote desktops or data duplication. Remote desktops keep the data and applications together at the main site while workers use local devices for access. Data duplication, using techniques such as a distributed file system or extended SQL server clustering, can also allow for data colocation -- or a managed cache of the data -- with the applications and users at the remote sites. Cloud-based deployments follow this same principle of data residency. If IT moves the applications to a cloud-hosted infrastructure -- whether it's web apps, Remote Desktop Session Host, VDI or desktops as a service -- the tendency is to move all of the data with them. But organizations should not automatically take that principle for granted. Instead, they should look at each case individually when it comes to determining data residency. The economics of data ...

Features in this issue

News in this issue

Columns in this issue