The was a fantastic design talk, thank you, it was exactly what I was looking for. There is so much garbage experts who talk about the basic of nosql or dynamodb and fail miserably to discuss the more import thing, schema design. You earned my sub just for this one video alone, keep up the great work! I've got an possible interview coming up and this is something I really needed to know sinice I'm only worked with sql database, but this role require nosql experience.
Gained lots from this video. I have been watching TH-cam videos for DynamoDB. Your method of 'Show and Why' went that little bit further of 'Show and Do This Way'. Your explanations help me understand why things are done as best practices.
This is all very cool. But seems like a lot of contortions and conventions to make up for the absence of things that something like mongo does out of the box with indexes, $lookup, ...
I have a controversy about this design. There is too much duplication. It forces the use of a unique name. It doesn't allow to use of non-uniq names I prefer to use ulid. It keeps unique and ordered. ulid ID has date in ID, ulid keeps an ordering
The best explanation of the design concept. I can see you must have spent a lot of time and effort to produce such a coherent presentation.
The was a fantastic design talk, thank you, it was exactly what I was looking for. There is so much garbage experts who talk about the basic of nosql or dynamodb and fail miserably to discuss the more import thing, schema design.
You earned my sub just for this one video alone, keep up the great work! I've got an possible interview coming up and this is something I really needed to know sinice I'm only worked with sql database, but this role require nosql experience.
Gained lots from this video. I have been watching TH-cam videos for DynamoDB.
Your method of 'Show and Why' went that little bit further of 'Show and Do This Way'.
Your explanations help me understand why things are done as best practices.
Great presentation. Practical callouts and commentary added so much to these otherwise familiar concepts.
This is a GEM.
this is a really great explanation, thanks for taking the time to put it together!
Thanks Tyler, great talk
Great explanation!!
Do you have plans to make some videos on ElectroDB? especially advanced concepts.
Interesting way to look at design
Tyler is gonna be a leader in this space within the next decade, hear him out!
Thank you!
This was excellent. Thank you Tyler. It's too bad you don't offer modeling services as a freelancer.
How would I get all courses that are in building01 and building02 etc
Great question, you can use the `between` sort key operator for that 👍
This is all very cool. But seems like a lot of contortions and conventions to make up for the absence of things that something like mongo does out of the box with indexes, $lookup, ...
I have a controversy about this design.
There is too much duplication.
It forces the use of a unique name. It doesn't allow to use of non-uniq names
I prefer to use ulid. It keeps unique and ordered.
ulid ID has date in ID, ulid keeps an ordering
theres nothing stopping you from building a composite key with timestamps.