AWS re:Invent 2021 - Data modeling with Amazon DynamoDB [REPEAT]

Подписаться 114 тыс.

Просмотров 28 тыс.

50% 1

In this session, learn about Amazon DynamoDB, a fully managed serverless database that provides high performance at any scale with built-in security, backup and restore, and in-memory caching. Hear from Alex DeBrie, Principal at DeBrie Advisory and AWS Data Hero, about the fundamentals of DynamoDB and how to use it as more than a key-value store. Data modeling for NoSQL databases like DynamoDB is different from modeling for traditional relational databases. Discover how to model complex requirements using simple building blocks. Also learn about primary keys, secondary indexes, and patterns for handling relationships, filtering, sorting, and more.
Learn more about re:Invent 2021 at bit.ly/3IvOLtK
Subscribe:
More AWS videos bit.ly/2O3zS75
More AWS events videos bit.ly/316g9t4
ABOUT AWS
Amazon Web Services (AWS) hosts events, both online and in-person, bringing the cloud computing community together to connect, collaborate, and learn from AWS experts.
AWS is the world’s most comprehensive and broadly adopted cloud platform, offering over 200 fully featured services from data centers globally. Millions of customers-including the fastest-growing startups, largest enterprises, and leading government agencies-are using AWS to lower costs, become more agile, and innovate faster.
#AWS #AmazonWebServices #CloudComputing

Наука

Опубликовано:

15 дек 2021

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 18

@mcmoodoo 2 года назад

What an amazing speaker!! Super concise, straight to the point, no fluff - pure value! Learned so much in an hour! Amazing. Looking to purchase his book and learn more. What a gem I've found today.....

@chrath9789 8 месяцев назад

this is pure gold, concise and effective , the way it should be

@galeop Год назад

Excellent talk, very clear and concise

@leaddeveloper2606 2 года назад

a must-watch video!

@maa1dz1333q2eqER 2 года назад

As always a great talk, thanks!!!

@Isom3250 2 года назад

great talk with good experiences/insights communicated

@galeop Год назад

40:59 if we wanted to know what’s the customer’s email, would it be best practice to duplicate the customer email in the App attributes section, rather than determine it from the PK ?

@lucasterable Год назад

1:01:19 New access pattern -> new GSI -> additionsl WCUs per write operation

@stevebuonincontri6853 10 месяцев назад

This was a great lecture - thanks for sharing.

@amazonwebservices 10 месяцев назад

You are welcome! So glad you like it! 😀 ☁️ 🤝

@ahmadmayahi Год назад

42:27 In this case, It's a filtering key not a sort key. For example, a User could have several Invoices (one-to-many), in this case the "SK" is a filtering rather than sorting. Correct me if I'm wrong.

@vermoidvermoid7124 8 месяцев назад

almost all data modeling videos don't cover eventual consistency issues with GSI, Thats cheating! I would like to know how to model data and keep strong consistency.

@anildasari Год назад

At 3:12 "DynamoDB is schema-less. That doesn't mean you shouldn't have a schema. You should absolutely have a schema. You should enforce it in the application layer." Why do NoSQL vendors promote "being schema-less liberates developers from the tyranny of RDBMSs", when all they're doing is pushing that responsibility to the application? Any database that doesn't support joins, forces rigid access patterns, enforces page size limits and throughput limits can give consistent, predictable read speeds 😀 DynamoDB is great for certain use cases, but the comparison with RDBMSs is unfair. They solve two different problems, and one can't replace the other.

@confuzler6985 Год назад

Because it is better, cheaper and way more flexible to have you schema enforcing rules or lack-off, on your business layer code rather than on the DB.

@jobrown04 7 месяцев назад

It comes from moore's law, as well. Data is cheap but CPU compute is expensive now. We no longer double CPU power every year, so SQL databases are difficult to scale with. This, to me, is why technology has moved to NoSql -> it's solving problems we didn't have 10 years ago.