Challenge seekers, here's an intriguing scenario for you.
#DistributedSystems
Imagine an application for user verification that asks for username, date of birth and other user details, and past addresses (town name, country).
The user can either select a town or manually enter one if it doesn't exist.
With every user onboarding, three things occur:
1. A User record is created if it doesn't already exist.
2. Town records are created if they don't already exist, ensuring unique combinations of town name and country.
3. The User and Town records are linked via a Many-to-Many relationship.
The twist: This application and its database are hosted across two data centers, one in India and the other in the US.
The question for you:
Can you foresee any potential challenges given this setup?
What kind of consistency, latency, and data replication issues might arise?
Are there other similar problems you can think of?
Have you worked on a similar problem? Would love to hear from you.
#Spanner #CockroachDB #CAPTheorem #DataConsistency #NetworkPartition
Disclaimer: Image for Representation purpose
Image Source: https://lnkd.in/gADGkPPk