Using Azure For Global Users -

i working on project whereby web site (all components hosted in azure) have both , international users. using blob , table storage 99% of data. not understand how setup global instances, including multiple tables, etc, , keep in sync. user logs site france, how can ensure hit same data center (which implies same storage instance)? if hit different storage instance, data not there and/or stale.

both compute , storage affinitized specific data center. there's no global compute or global storage deployment concept.

having said that: you'll typically host human-facing app (e.g. web app) in single data center. usually, latency between browser , server not of issue if relatively-small quantity of data moving between two. majority of bandwidth typically between web server , app servers and/or database instances. , in azure, data doesn't need colocated in same data center web app (though it's ideal scenario latency + egress bandwidth cost perspective).

if want compute in multiple data centers, you'd need have higher-level mechanism doing type of load balancing (such azure's traffic manager). however, traffic manager's "closest" setting, you're not guaranteed user in france hit w. europe vs. n. europe data center. you'd have plan visitor hitting any data center. why it's simpler deal compute in single data center.

regarding data: if compute in single data center, there's no need (other disaster recovery) write data multiple data centers. if do decide deploy compute multiple data centers, you'll need own method syncing data. azure blobs & table storage, can consider type of command pattern (e.g. cqrs) operations queue driven. allows process each queued data operation against multiple storage accounts across different data centers.

now, might have data sovereignty issues, data must reside in specific data center specific customers, based on geo. again, you'll need implement in app layer. 1 thought on affinitize user particular data center when set (and store data center mapping in single database along web tier). @ point, when visitor logs in, can correct data center and, within browsing session, access data specific data center.