7 Common DynamoDB Patterns for Modeling and Building an App with Alex De Brie

[@UnknownIdentityDE]

The best DynamoDB tutorial I have seen to date. I love the clean and simple code.

[@simranbayas810]

OMG, didn't see this coming. "Marcia and Alex" Dream Team, period.

[@foobar_codes]

thankss :D

[@ediancomachio2783]

THIS IS AWESOME! I'm so glad I've subscribed to this channel

[@WisoAp]

Thank you for this video :) Spanish community deserves this awesome stuff as well!!

[@foobar_codes]

Hahhaa now i need to find a Spanish version of alex 🤷🏽‍♀️

[@apidas]

Thank you so much Marcia and Alex for making this video possible

[@dbs1uk]

This is an excellent non-trivial example. It's also the cleanest approach to working with DynamoDB that I've seen to date 👏👏👏

[@foobar_codes]

Thanks! Alex is amazing

[@jpablonov]

Muchas gracias Marcia por esta excelente entrevista con Alex!!!!! Saludos desde argentina!!

[@BrendanGrainger]

Thank you so much for this Marcia and Alex. This was so helpful.

[@jdd1955]

This was incredible, i've been using DynamoDB for awhile now and this helped reinforce something that I have been doing as well as answer a few questions on some best practices and provide ideas on how to design future projects. Thank you so much Marcia and Alex.

[@foobar_codes]

Great to hear!

[@nicolasaguilar9209]

same here

[@engineforce]

Thanks so much for this video and having table of content in your descriptions is really useful.

[@foobar_codes]

Happy that it helps

[@garywaddell6309]

Alex is world class, he has so much integrity, I’d support anything he produces 🙌🏻

[@foobar_codes]

he is great :)

[@garywaddell6309]

@@foobar_codes And of course you are too Marcia :)

[@abhinavkapoor321]

@@foobar_codes Sure Alex is great, but Marcia it is awesome how you ask questions from your guests to get more details that otherwise could be taken for granted by subject matter experts. Thanks a lot for the awesome content.

Excellent contribution, I heard about his DynamoDB book and this video fits perfectly as an introduction.

[@tringuyenucminh167]

It's very helpful for me. Thank you so much Marcia and Alex ^^

[@foobar_codes]

Happy to help!

[@AndiFotschl-dy2vb]

Thx Marcia! Having seen this video, makes the DynamoDB setup so much more human in the project I'm working on. 🎉

[@foobar_codes]

Great to hear

[@bisadelara5933]

Thanks so much ! Appreciate the effort of bringing all this content !

[@foobar_codes]

Glad you enjoy it!

[@MrJulito88]

Great presentation of DynamoDB possibilities

[@Johnathanaa7]

Great video, loved the way you all walked through the steps of designing

[@foobar_codes]

Thank you! Cheers!

[@uzair004]

not only great dynamodb video, but for coding best practices as well. I have been working in a project from a while & we are using these ulid, re-usable componenets/methods, excel sheets for access patterns. found the source probably :D

[@benjaminiduwe2958]

Great content, I learnt a lot from this video.

[@foobar_codes]

Awsome! Thanks for the message

[@56faisal]

Wow! this is really great stuff! Thank you both for this :D

[@foobar_codes]

Our pleasure!

[@Deiefe]

This is great, thanks heaps both for these explanations!

[@foobar_codes]

Glad it was helpful!

[@ivorpad]

This was really good. Learned tons about DDB. I didn't know about ULIDs either 👍

[@foobar_codes]

yes ULID lib is great!

[@RicoMinovo]

Thanks! Nicely explained at a high and low level .

[@jeffreypalma4498]

Thank you. Good class.

[@cristianpallares3847]

Love ulid! I was already using it with DynamoDB and the ordering property is awesome.

[@foobar_codes]

Yesss this library is really useful

[@cristianyesid99]

Thank you very much for the video!

[@rickfarina9835]

Excellent... I like the use of TypeScript and the abstraction to simplify access. Really well done and informative. Still have questions though on writing DDB Single Table app when working with legacy system where entities already exist. Would like to hear more about that. Again, Excellent presentation!! Thank you Marcia and Alex!

[@alambertt]

No puede ser... Hoy mismo estaba viendo este mismo tema 🤯🤯🤯🤯 Wow Gracias Marcia. Me gustaría un vídeo ahora en español. De todas formas este lo voy a ver. Gracias 😊😊😀

[@foobar_codes]

este video no creo que pueda estar en español tal cual, ya que alex solo esta en ingles. pero seguramente hare una serie de dynamo en español en el futuro. que bueno que te gusto este video

[@alambertt]

@@foobar_codes excelente 👍🏻🤗 Esperaremos la serie de DynamoDB con ansias. Es una excelente BD. Ya vi los Reinvent 🤯 Realmente es genial

[@vardaanaashish6753]

Fantastic content!

[@foobar_codes]

Thanks

[@tkjnnmf5315]

Really useful channel Thx!

[@foobar_codes]

Happy to help!

[@b1021]

Given the model shown, how would you query the table to return all users?

[@ryandsouza2962]

Awesome video! DDB is ♥️

[@foobar_codes]

It really is!

[@GilluanFormiga]

Nice video.

[@squidwurrd]

Got the book!

[@Trademm]

What i needed

[@yassermh5851]

How would you get all the photos of the people a user follows? like in the home page of instagram, it shows all the photos of the users you have followed. Do you query all the followed of that users and then query each of them one by one to see if there is a new photo?

[@SergioAdonis]

Este video es oro

[@aminebioudi8414]

what a great explanation ... i do have one question: why on the sheet file we have main table for list likes for photo and not for list comments for photo ?

[@HaibertBuilds]

I feel like I gotta watch this 4 times to get my brain to actual consume all of this and digest it. Im legit hating myself for trying to learn noSQL lol

[@omar-salim]

thanks for the great tutorial, I have a question though, how to list down unfollowed users? in order to follow a user the application needs to provide a set of unfollowed users, right ? I don't think we should design an access pattern for this. The only solution in my mind is perform a fake join at the lambda code level which is discouraged when using DynamoDB. Any better suggestion?

[@jean-louisgouwy]

It was really helpful to understand the basic of the one-single-db pattern. But one question, for example,, you put the User entity in the same table than follows, photos, etc ... But usually, in a microservice-based company/project , we will have a "user service", "media service", "post service" which will manage all their own business rules, right ? So concretely, in that case this pattern is still useful ? Or you duplicate data to avoid to make some proxy endpoint ?

[@Brajgamer]

I think it depends on the team compositions. First thing is that microservices are primarily for teams autonomy. So if we keep the teams autonomy then i think table per microservice is good. If we have a central authority for db like a dba then i think we can have a single table design.

[@CosmosCR]

The simplest thing i cant seem to figure out with dynamo.. How would go get a list of users who follow both "foobar" and "alex"? Or users who liked 2 different phots?

[@michaelkrison]

Awesome..

[@foobar_codes]

Thanks 🤗

[@rohitkochar9022]

Amazing talk as always Alex. Love your videos and I have learnt a lot. One quick qs. I created a GSI on one of the date column but since I have to do a between , I had to use scan operation. Is this a bad way to get data? I can use index with query but that won't let me do any between.

[@AntonRand90]

Great video 🎉 Should ULIDs only be for Sort Keys rather than a PK? I thought a PK should ideally generate values that will be evenly spread over partitions. I like the concept of ULID but does it increase the risk of hot partitions much?

[@mohamedjavithurrahuman2218]

Useful

[@foobar_codes]

Glad you think so!

[@kvsantosh]

Good video. One question on scalability, lets say a photo gets multiple millions likes, in the current schema all the likes will have same PK. Do we not run the risk of hitting the limits of 10GB size limit per partition?

[@Brajgamer]

Yes we do, in that case one patter which i have used is that you pick a set of numbers let's say 1 to 100, and then whenever you store a like you just suffix or prefix a random number from that set in the sort key. That way your million likes would be distributed in 100 different partitions. Then you can keep a total count separately just like he did in this video with the likescount using transaction.

[@rajpanchal9226]

This schema design is not suitable for search at all. I need a tutorial on a searchable dynamoDB design.

[@sashikadulaj5209]

Really helpful