You can also use Global Tables to migrate from one AWS Region to another. Add a new region, wait until it replicates, then delete the old region. Data migration done!
Yet another great video., so informative and so well explained. I keep looking for updates on your channel to not miss any.... Was wondering, do you plan on creating some videos that talk about AWS Networking stuff ?
Hi, thanks for the awesome video! I have one question, what happen in below scenario: Imagine Table User has auto increment column as UserId, Person A creating a record from Asia region Person B creating a record from Europe region both happening at the same time, There's a chance of creating same auto increment Id in both region's table and it will make issues will doing synchronisation?
That's a good question. Specially with the eventual consistency, i wonder if it would increment twice or once. (leaving message here, just incase he sees your question and replies)
Hi Santhos, great question. In this case, Global Tables would apply its 'Last Writer Wins' policy. This is a form of strong eventual consistency. A side affect of global tables is that for a split second, the content will be out of date for Person A's record in Asia. Hope this helps.
During a situation when one region goes down and one application is trying to fetch data from DynamoDB, will the global table functionality serve the data from some replica automatically?
Well made video that served my purpose of a visual introduction.
Thanks Vimal!
You can also use Global Tables to migrate from one AWS Region to another. Add a new region, wait until it replicates, then delete the old region. Data migration done!
Beautiful! I hadn't even thought of that, but thats an amazing tip. Thanks Kirk!
@@BeABetterDev p0o
Great video! Thanks!
Yet another great video., so informative and so well explained. I keep looking for updates on your channel to not miss any.... Was wondering, do you plan on creating some videos that talk about AWS Networking stuff ?
Thanks so much Pranay! VPC / Networking topics have been on my backburner for a while. I'll try to prioritize them in the coming months. Cheers.
Great Tutorial!!
Thank you!
You're welcome!
hey can you make a video on EKS and also I came to know that there is an AWS cloud practitioner certificate, what are your views on that certificate
Hi, thanks for the awesome video!
I have one question, what happen in below scenario: Imagine Table User has auto increment column as UserId, Person A creating a record from Asia region Person B creating a record from Europe region both happening at the same time, There's a chance of creating same auto increment Id in both region's table and it will make issues will doing synchronisation?
That's a good question. Specially with the eventual consistency, i wonder if it would increment twice or once. (leaving message here, just incase he sees your question and replies)
Hi Santhos, great question.
In this case, Global Tables would apply its 'Last Writer Wins' policy. This is a form of strong eventual consistency.
A side affect of global tables is that for a split second, the content will be out of date for Person A's record in Asia.
Hope this helps.
Hi Ashan, see my answer to Santhos regarding this question if you are interested.
@@BeABetterDev thanks a lot..
During a situation when one region goes down and one application is trying to fetch data from DynamoDB, will the global table functionality serve the data from some replica automatically?
Folks, I understand that this is similar to s3 cross region replication. But what about SQL DB? do they have features like streams/write-to-replicas?
Yes - use global databases with RDS Aurora. This works with MySql or PostGres engines.
You need to come up with a AWS Solution Architect Udemy course. You teach a lot better than those at Udemy
Hi Kumar, this is something I'm working on as we speak :)
@@BeABetterDev Any ETA ?
This video says that "oldest timestamp (took place first) wins" - but isn't it "last writer wins" - where the most recent timestamp wins???