Okay . As far as we know Dynamo Db has great availibility rather being a consistent right? So what happens when network partitioned happens and we query, aren't we get the data as inconsistent mode rather than being consistent across different nodes . Atleaset this what i'm assuming as per CAP theorem which follows strongly AP for DYNAMODB. Am I in a right track ? Btw this looks dope! Keep on rocking.
great video thanks a lot for the same, just wanted to ask if I want to replicate the Data between two Dynamo DB tables but in the "same region" how can is do it, use case is - one Dynamo DB Table will be used Write data and another Dynamo DB table will be used to read only, please suggest strategy...
Based on the formula, if I have a requirement of 3000 rcu and 1000 wcu, the table will initially create 2 partitions. But why need 2, why not 1 ??. 1 partition is sufficient for the requirement. Assume data size is under 10 GB. Please anybody care to explain ??
DynamoDB might start with 2 partitions instead of 1 for your requirements of 3000 RCUs and 1000 WCUs to better balance the load and improve performance consistency, even if one partition can technically handle the capacity. This approach also enhances fault tolerance and operational flexibility by distributing the workload across multiple partitions from the start.
@@Pythoholic I think, I have figured out why 2 partitions are needed and not 1. One partition can deliver either 3000 rcu or 1000 wcu or mix of both (i.e. if it has 500 wcu it can have 1500 rcu). It is not possible for a partition to deliver both 3000 rcu and 1000 wcu. By this logic, if one partition delivers all the required 3000 rcu, one more partiton is required to deliver 1000 wcu. Since they are distributed equally among partitons, each partition will deliver 1500 rcu and 500 wcu.
The thing which is missing from most documentation online, is its not 3000 rcu and 1000 wcu. Its 3000 rcu or 1000 wcu or a mix of both. By this logic, one partition won't be able to handle that load. You must need two. I got this information from an AWS Events video posted on YT about DynamoDB.
If you are using PostGres or MySQL already and if you want to migrate to AWS, you would prefer using Aurora, like if your data is entity-relationship based you should use Aurora. Else if you planning to host data ie document based or JSON based or Column based, like for example Cassandra Mongo Db type data. You should use Dynamo DB.
the way you have cleared things ...nobody can...thankyou so much 🙏
Please explain encryption at rest and encryption in flight
Great work done and very well explained. Keep up the good work.
Wonderful Presentation Sir, Thank you very much for spending all your valuable time for us ...!!
The explanation and slides were top notch.. Kudos keep it up...You earned a subscriber.
Thanks for the support
Great work Pythoholic, the way you describe the topics its really helpful to me to learn this course, I am really enjoying your presentation.
Good job , very well done
Really great presentation. Appreciate your willingness to share knowledge with others. That is a virtue.
Thanks 👍
Okay . As far as we know Dynamo Db has great availibility rather being a consistent right? So what happens when network partitioned happens and we query, aren't we get the data as inconsistent mode rather than being consistent across different nodes . Atleaset this what i'm assuming as per CAP theorem which follows strongly AP for DYNAMODB. Am I in a right track ? Btw this looks dope! Keep on rocking.
Very good explanation.
Hi Pythoholic. It is really good lecture especially the visuals. We would also like to see Demo on DynamoDb it would really be great. Thanks
yes thats coming up
thanks for the feedback
great video thanks a lot for the same, just wanted to ask if I want to replicate the Data between two Dynamo DB tables but in the "same region" how can is do it, use case is - one Dynamo DB Table will be used Write data and another Dynamo DB table will be used to read only, please suggest strategy...
Really, great explanation.
Great work
Based on the formula, if I have a requirement of 3000 rcu and 1000 wcu, the table will initially create 2 partitions. But why need 2, why not 1 ??. 1 partition is sufficient for the requirement. Assume data size is under 10 GB. Please anybody care to explain ??
DynamoDB might start with 2 partitions instead of 1 for your requirements of 3000 RCUs and 1000 WCUs to better balance the load and improve performance consistency, even if one partition can technically handle the capacity. This approach also enhances fault tolerance and operational flexibility by distributing the workload across multiple partitions from the start.
@@Pythoholic I think, I have figured out why 2 partitions are needed and not 1. One partition can deliver either 3000 rcu or 1000 wcu or mix of both (i.e. if it has 500 wcu it can have 1500 rcu). It is not possible for a partition to deliver both 3000 rcu and 1000 wcu. By this logic, if one partition delivers all the required 3000 rcu, one more partiton is required to deliver 1000 wcu. Since they are distributed equally among partitons, each partition will deliver 1500 rcu and 500 wcu.
The thing which is missing from most documentation online, is its not 3000 rcu and 1000 wcu. Its 3000 rcu or 1000 wcu or a mix of both. By this logic, one partition won't be able to handle that load. You must need two. I got this information from an AWS Events video posted on YT about DynamoDB.
Great work man
when will we use Aurora DB and Dynamo DB?
If you are using PostGres or MySQL already and if you want to migrate to AWS, you would prefer using Aurora, like if your data is entity-relationship based you should use Aurora.
Else if you planning to host data ie document based or JSON based or Column based, like for example Cassandra Mongo Db type data. You should use Dynamo DB.