I watching two times for understand this is the best series for start the modeling help me to undertand many things in the end all is so clear thnx so much for this series from mexico.
What a brilliant video! Probably the only video that walk thru a design phase! Love it! So much to learn. With this series, I am very confident I will complete my app with DynamoDB! Much thanks!
Simply brilliant - apart from proper modeling, biggest benefit of this VDO is discussion on "pros and cons" of each decision - plz keep posting such use cases. You have awesome thought process and presentation skill.
Nice video ! I ended up close to your final thoughts. 4 access patterns solved by the table and 3 by GSI. Regarding the table I prefer to have a sort key with value #info or booking#bookginId to be able to fetch info of a property or all its bookings. For GSI location I prefer to have country as PK and city as SK to be able to fetch all property of a country. For GSI userId I ended up with a SK propertyID but I prefer yours with the starting date to be able to sort with a date. For GSI ownerId I perfer to have the SK the same as the table to have the info and bookings straight forward. I tried the dynamoDB workbench. It's very useful. Don't hesitate if you want to compare with my model. Thanks again for all your videos !
hello, thank you for sharing this video, i have a question about GSI3. the sort key is the property_id, i was expecting to see "property" again as we're requesting all properties. while scaning do we know the property_id?
Great video thanks for sharing, I am new to DynamoDB and find it very useful, the only part I found confusing is when you mentioned that you are using only one table, I thought you had at the end two different tables because they have different Primary Keys, does it mean that DynamoDB can have more than one primary key definition in a single table?
@@foobar_codes Thank you so much for quick response, got a question. So the attribute we define for a DynamoDB should be a key schema or GSI/LSI? So what should we do if there are more number of attributes which we dont want to be part of keyschema or GSI/LSI?
I'm confused. Do we end with one table or two? I ask because it's possible to have 1 composite key with multiple indicies (GSI & LSI) on a single table but you can't have multiple composite keys on a single table in dynamo like we seem to have at the end of this video.
Based on this one-table model, after a USER signs up for an account, I assume we have all the user's information like user_id, address, city, phon_number Etc. We can locate a user using the GSI. I get that. But we must have values for the table's primary key and sort key. What do we use? The user account has no property_number or booking_date because those records aren't yet related to properties in any way. Also, how do you put the string "property" in a date field? Isn't that field of type, number (i.e, unix timestamp)?
@@foobar_codes si, por favor... es que quiero entender bien el uso de DynamoDB y tus videos me han servido mucho... he estado revisando mucho pero tus videos estan bien explicados... y traducirlo con youtube es patetico.. no se entiende nada
Really interesting, but as usual, sometimes we do not have all the requirements access at the beginning of the project. The PO could come later with another access, such as : Ok now, we need to get properties available between two dates. How do you handle this when it could "break" your first access patterns ?
You have probably already solved this, but you can add a global secondary index if your app allows for downtime, otherwise if you need a local secondary index or can't have downtime you would have to copy your table into a new table with your new index added in the setup process
@@jesse9999999 we added a GSI indeed, but it was complicate because initially, the value was in a nested attributes. As we can't create a GSI based on nested property, we had to duplicate the information at the root. Not really pretty.
Love this video! I really enjoyed the discussion on design iterations. Thanks for this nice exploration of the schema design process in NoSQL.
I'm a fan of your reinvent talk so this comment makes me very happy :D
I watching two times for understand this is the best series for start the modeling help me to undertand many things in the end all is so clear thnx so much for this series from mexico.
What a brilliant video! Probably the only video that walk thru a design phase! Love it! So much to learn. With this series, I am very confident I will complete my app with DynamoDB! Much thanks!
Very well explained, nice and compact. Thank you for this.
the last 2 chapters were super important, and still relevant 3 years later.
Best part, schema design process, love it
Simply brilliant - apart from proper modeling, biggest benefit of this VDO is discussion on "pros and cons" of each decision - plz keep posting such use cases. You have awesome thought process and presentation skill.
Nice video ! I ended up close to your final thoughts. 4 access patterns solved by the table and 3 by GSI. Regarding the table I prefer to have a sort key with value #info or booking#bookginId to be able to fetch info of a property or all its bookings. For GSI location I prefer to have country as PK and city as SK to be able to fetch all property of a country. For GSI userId I ended up with a SK propertyID but I prefer yours with the starting date to be able to sort with a date. For GSI ownerId I perfer to have the SK the same as the table to have the info and bookings straight forward. I tried the dynamoDB workbench. It's very useful. Don't hesitate if you want to compare with my model. Thanks again for all your videos !
That is great that you tried the example and shared your results :D
hello, thank you for sharing this video, i have a question about GSI3. the sort key is the property_id, i was expecting to see "property" again as we're requesting all properties. while scaning do we know the property_id?
I always enjoy your videos. Teaching isn't as easy people think. Great video.
Thanks a lot 😊😊😊
Great video, thanks. It would have been good to see a discussion about GSI Overloading (including the PK, SK, Data pattern).
Noted
Excellent. Cant wait to see your coming videos
I hope you like then 😊😊😊
Nice energetic vid! Together with some vids on Cassandra I feel like I'm very well equipped to start experimenting with things
Go for it!
Gracias por el video . De casualidad tienes el video es español ?
No de esto no tengo en español 😓
Muchas gracias. Buen video.
Just awesome video, one question do aws proserve team or premium support design the data models in dynamo DB? Fro some particular project?
Great video thanks for sharing, I am new to DynamoDB and find it very useful, the only part I found confusing is when you mentioned that you are using only one table, I thought you had at the end two different tables because they have different Primary Keys, does it mean that DynamoDB can have more than one primary key definition in a single table?
Yes you can have different data stored in one table. Mixing different type of ítems.
Thank you, can you please share sample dynamodb cloud formation template you used for this?
github.com/mavi888/fireBnB-dynamo
@@foobar_codes Thank you so much for quick response, got a question. So the attribute we define for a DynamoDB should be a key schema or GSI/LSI? So what should we do if there are more number of attributes which we dont want to be part of keyschema or GSI/LSI?
I'm confused. Do we end with one table or two? I ask because it's possible to have 1 composite key with multiple indicies (GSI & LSI) on a single table but you can't have multiple composite keys on a single table in dynamo like we seem to have at the end of this video.
Based on this one-table model, after a USER signs up for an account, I assume we have all the user's information like user_id, address, city, phon_number Etc. We can locate a user using the GSI. I get that. But we must have values for the table's primary key and sort key. What do we use? The user account has no property_number or booking_date because those records aren't yet related to properties in any way.
Also, how do you put the string "property" in a date field? Isn't that field of type, number (i.e, unix timestamp)?
Hola, Excelentes tus video.... Crees que puedas hacer videos relacionados a DynamoDB pero en español...
si le pongo subtitulos? seria de ayuda?
@@foobar_codes si, por favor... es que quiero entender bien el uso de DynamoDB y tus videos me han servido mucho... he estado revisando mucho pero tus videos estan bien explicados... y traducirlo con youtube es patetico.. no se entiende nada
Really interesting, but as usual, sometimes we do not have all the requirements access at the beginning of the project.
The PO could come later with another access, such as : Ok now, we need to get properties available between two dates.
How do you handle this when it could "break" your first access patterns ?
You have probably already solved this, but you can add a global secondary index if your app allows for downtime, otherwise if you need a local secondary index or can't have downtime you would have to copy your table into a new table with your new index added in the setup process
@@jesse9999999 we added a GSI indeed, but it was complicate because initially, the value was in a nested attributes. As we can't create a GSI based on nested property, we had to duplicate the information at the root. Not really pretty.
Have you tried modeling this with NoSQL Workbench?
i have played with it :) its quite a nice tool