AWS DynamoDB (Internals) Masterclass with Alex Debrie

No video

AWS DynamoDB (Internals) Masterclass with Alex Debrie

Рет қаралды 13,730

The Geek Narrator

Күн бұрын

Пікірлер: 37

@garywaddell6309 Жыл бұрын

Something to consider. If you use the aggregation use case for streams, consider storing the counter columns in a different dynamo table. If you use one table, the update for the counter will trigger your lambda stream again and you can get into an endless loop of lambda execution unless you code for it appropriately, but you have to be careful. Using 2 tables allows you to use one stream on your primary and no streams are necessary on the aggregation table.

@zishanshaikh9375 7 ай бұрын

You're doing a great job with these podcasts, please continue making more such deep dive videos

@TheGeekNarrator 7 ай бұрын

Thanks a lot 🙏🏻

@VJBHARADWAJ Жыл бұрын

This is so good. Thank you so much, you asked most of the questions I had in mind, and not just glossing over. Also really appreciate your effort on drawing, thank you so much ❤

@TheGeekNarrator Жыл бұрын

Thank you 🙏🏻😀

@SunilKumar-hv1gt Жыл бұрын

Great video with simple explanation. Waiting for a podcast on SOLID principles.

@TheAgb01 Жыл бұрын

Kaivalya, This was the second episode I heard from your channel. Hooked to it. Must say that the choice of speakers, the questions you asked was top notch. I can see the efforts you've put in. Keep going 💪

@TheGeekNarrator Жыл бұрын

Thanks a lot 🙏🏻😀

@ChrisShenton Жыл бұрын

I really enjoyed the deep dive, it helped clarify some DDB limitations (that exist to provide predictable performance). I'm looking forward to a future talk on DDB data modelling!

@TheGeekNarrator Жыл бұрын

Thanks Chris. Data Modelling episode will be recorded soon.

@mhmdbahja Жыл бұрын

Very informative podcast, thank you, especially for the drawings

@TheGeekNarrator Жыл бұрын

Thank you 🙏🏻😀

@tanishqsaini4217 7 ай бұрын

Thank you for the great podcast 🔥, looking for more like this.

@TheGeekNarrator 7 ай бұрын

Thank you 🙏🏻😀

@JardaniJovonovich192 Жыл бұрын

Great video. Excited for part 2

@TheGeekNarrator Жыл бұрын

Thanks for watching 🙏🏻 Part-2 is coming soon.

@renatoargh Жыл бұрын

Amazing session, guys! Thank you so much for the content. I will subscribe and also take a look at Alex's book! Keep up the amazing work!

@TheGeekNarrator Жыл бұрын

Thank you so much for watching and subscribe. I am really glad you liked it. 🙏🏻

@anandapte9166 Жыл бұрын

One of the best dynamodb deep dives I have listened to. Looking forward to the data modelling episode.

@totox6886 Жыл бұрын

Subscribed your channel in hope of learning good stuff here.

@TheGeekNarrator Жыл бұрын

Thank you 🙏🏻 Hope you find good learnings. Always feel free to provide feedback. 😀

@sauravshukla2492 9 ай бұрын

Can we have similar video for redshift as well . BTW these videos are really helpful😊

@TheGeekNarrator 9 ай бұрын

Thank you 🙏🏻 noted.

@stevebuonincontri6853 Жыл бұрын

Alex - what about headless CMS - I tried to create using dynamoDB one year. Has any companies attempted this?

@sumeetsingh1729 6 ай бұрын

50:00 when leader node gets down, this may cause inconsistency right? 1. Request arrived to update an item. 2. Leader node updated. 3. Change forwarded to Replica_A. 4. Leader node crashed 5. Change persisted in Replica_A. 6. Replica_B never saw this change and was elected new leader. How DDB handles this?

@TheGeekNarrator 6 ай бұрын

Thanks for your question. Depends on the read consistency levels. DDB supports strong consistency as well, in which case the update won’t be considered done if the write to replica fails. So basically you need to choose what consistency levels you need. (They provide discounts on low consistency reads, but please confirm this, as things may change). I hope it answers?

@sumeetsingh1729 6 ай бұрын

@@TheGeekNarrator thanks for answering. Lemme add another complexity here that Replica_A was able to ACK back to leader, whereas Replica_B didn't see this change. Now, if Replica_B is elected the leader, then the new replica spawned, (assuming) will copy from Replica_B. Since, that write succeeded and the client received success response, but the next time same item is fetched, it'll be a stale one. Doesn't this break the notion that DDB is a CP system?

@sumeetsingh1729 6 ай бұрын

Also, since strongly consistent reads go to the leader rather than replica, we'll get stale data in the above scenario.

@RiteshMalav 2 ай бұрын

DDB, would never choose a node to be leader in case it is not up to date. This comes when paxos does the leader election it each node has to tell it's state in the election only if it is up to date it gets elected as leader

@amanuelyohannes7151 9 ай бұрын

Hi, thank you for the contents!!! What is the annotation software you are using, if you don't mind me asking

@TheGeekNarrator 9 ай бұрын

Thanks. I use excalidraw for diagrams, canva for some visuals and descript for editing.

@chiragr1336 Жыл бұрын

When is the session on jvm? I want to master it.

@TheGeekNarrator Жыл бұрын

Coming soon. Possibly in two weeks. Could you elaborate on what exactly you want to learn?

@shreyasshivakumar8578 Жыл бұрын

Can you please recommend any resources to understand more about database internals

@TheGeekNarrator Жыл бұрын

Have you looked at the Database internals book? Do check it out. A good start can also be the episode I did with Franck Pachot Part 1 - Database Internals with Franck Pachot kzfaq.info/get/bejne/es98dJODzpy2lo0.html