We use analytics cookies.We use cookies to analyze site traffic and improve your experience.
Loading...
System Design Masterclass · Data Replication Distribution
Free preview: the first 2 parts of this 6-part lesson.
Already bought the course? Sign in to read the whole lesson.
this lesson is part of
System Design Masterclass
Unlock this lesson and the 751 other paid lessons
$25 once, by PayPal
See the System Design courseread the rest of this lesson in
System Design Masterclass
Unlock this lesson and the 751 other paid lessons
$25 once, by PayPal
See the System Design coursein Data Replication Distribution
This lesson is part of the full System Design Masterclass. Unlock it along with 769 other lessons for a one-time payment.
One-time payment: UPI, card or netbanking
Get Lifetime Access18 Foundation lessons are free, no payment needed. Try them now
It is easy and good
“It is really nice and good Please join the course”
In 2018, GDPR went into effect. Suddenly, European user data couldn't just be shipped to a US data center without legal justification. Companies scrambled. Many had been running everything from us-east-1 with no European presence.
Then India's data localization rules followed. Then Brazil's LGPD. Then China's data security law. Country after country started requiring that certain categories of data, personal information, financial records, health data, must reside within their borders.
Geo- isn't just about performance anymore. It's about legal compliance. You need European user data in European data centers. Indian financial data in Indian data centers. And simultaneously, you might need a global view of all data for analytics, fraud detection, or customer support.
This is a harder problem than cross-region replication for DR. With DR, you're just copying everything to a backup region, the simpler case the cross-region replication lesson covers, including how far behind the copy runs. With geo-replication for compliance, you need to control exactly which data goes where, based on jurisdiction, data type, and regulatory requirements.
There are three patterns, each with a different compliance posture:
Full geo- gives optimal read performance but replicates EU user data to US data centers, violating GDPR without legal basis. Selective geo-replication offers per-table control but is complex to configure. Geo-partitioned replication is the standard compliance-safe approach: partition by geography, each region owns its data.