DynamoDB is an example that not all No-SQL databases are designed equal. DynamoBD is very strict in the design of access patterns, if you need to perform a query with a query method and you don't have the necessary index (and if it is composite you must concatenate it in a column) it will be difficult for you to access it efficiently, it requires more careful planning than other DBs
TBH, responsible engineers should apply thoughtful planning - even with traditional relational DBs, especially with indexes for access patterns. it would be really embarrassing to experience slowdowns in prod just because someone forgot about an index and executed a full table scan 🤣
Right, DynamoDB aims to be fast and efficient. You can't push unbounded work onto the database. You must consider your update and access patterns as part of the schema design.
Great question, Harikrishna. 🧐 See this guide on choosing the right database to start with: go.aws/46Dnf95. You can find information on the different types of databases and available services on AWS. You may also find this best practices guide for databases helpful: go.aws/3tF6TOM. ✅ ^MO
Wow! The best use of 45 minutes of my life. Very efficient quality information on DynamoDB. Kudos to the presenter for the preparation!
Thanks for the feedback! We're happy to hear that you enjoyed the video. 😀 ^AK
One of the richest videos I’ve seen about DynamoDB. Thank you
Thank you @jasonhunter for this presentation. Your structure and flow seemed very fluid to me and very helpful.
Thank you! I appreciate that.
Great presenter! Very easy to follow
🙌
Useful technical info from 30:15 onwards
Thank you. The initial sales pitch is unbearable.
thanks! Wasnt interested in the C-level nonsense for the half hour
Very well done presentation! Informative with no filler.
DynamoDB is an example that not all No-SQL databases are designed equal. DynamoBD is very strict in the design of access patterns, if you need to perform a query with a query method and you don't have the necessary index (and if it is composite you must concatenate it in a column) it will be difficult for you to access it efficiently, it requires more careful planning than other DBs
TBH, responsible engineers should apply thoughtful planning - even with traditional relational DBs, especially with indexes for access patterns. it would be really embarrassing to experience slowdowns in prod just because someone forgot about an index and executed a full table scan 🤣
Right, DynamoDB aims to be fast and efficient. You can't push unbounded work onto the database. You must consider your update and access patterns as part of the schema design.
Good Observation: i see this as an upside. Others will see it as a downside and probably just us a different tech.
Excellent explanation of DynamoDB. It's very helpful.
Thanks! We're so glad you like it! 😀
This was phenomenal! Thank you!
Excellent video
Perfect Explanation. Thanks a lot!
It's our pleasure, Akhil! 😁 Glad you liked it! 😀
thnx, this was actually interesting
Excellent presentation, thank you.
how we will decide which database we should choose to an work
Great question, Harikrishna. 🧐 See this guide on choosing the right database to start with: go.aws/46Dnf95. You can find information on the different types of databases and available services on AWS. You may also find this best practices guide for databases helpful: go.aws/3tF6TOM. ✅ ^MO