Amazon DynamoDB: Chat Data Model with DynamoDB (Single-Table approach)

I’ve been working with noSQL databases for a while now (I actually haven’t written an SQL query for years— not until I started working with Amazon Athena recently). There is a noSQL database for almost every use-case: time-series data, JSON/BSON documents, geo-spacial and graph data, etc. Unlike relational databases, each noSQL database covers a particular niche, or multiple niches. Each should be considered for specific workloads rather than a catch-all (the way relational databases used to be utilized). Since we’re architecting a chat application which requires a significant amount of key lookups and fast writes/reads, DynamoDB is a perfect fit.

[muhammadmusharaf]

Hey Vladimir, It really helped me and cleared a lot of confusions.🙌🙌

[MrCatastropha]

Great video!
How about getting sorted conversations by last message time?

[shredcrew]

This is nice, but a really common use case would be getting the chats ordered by the most recent message.

[Ethlon]

What if it is a multi-tenant chat app? How would you model that? TenantId as PK? Just curious on your thoughts. Great info. Thanks for posting!

[VenuGopalVallepu]

How do we model if we need tlo query based on timestamp with in between dates

[arpitanand]

Hi, thanks so much for this video. This really helped me a lot. I just have a question: As the data grows eventually it will quickly reach very large say, billions or may trillions!.. So how will AWS manage those very large data? will the single table design not be a problem then?