I see Alex, I watch and I like! What a session! Every year I anticipate that this will be a generic dynamodb session, every year Alex proves me wrong. Loved the examples and the reasoning behind the modelling, Alex. You really should do these in other aws events too.
Amazing technology but, damn. Choosing SQL is so much easier. It’s hard to justify this kinda mental overhead just to manage a db. You need to have a very real reason to not use SQL in my opinion.
While the explanation is up to the point ! scalable database but, it sacrifices flexibility! Directly designing the ER (Entity-Relationship) for DynamoDB why invest time in learning it when it's not open-source? after few years aws might abandoned this product
I see Alex, I watch and I like!
What a session! Every year I anticipate that this will be a generic dynamodb session, every year Alex proves me wrong.
Loved the examples and the reasoning behind the modelling, Alex. You really should do these in other aws events too.
Thanks, great job. I always find your talks informative and tailored to the developer.
I will use Dynamodb if I am Alex myself, or my access patterns are very simple and I know them upfront :) , very informative talk
Watching you for a while. I can tell you didn’t feel well. But still a great session!!!
Amazing technology but, damn. Choosing SQL is so much easier. It’s hard to justify this kinda mental overhead just to manage a db. You need to have a very real reason to not use SQL in my opinion.
Yeah we're totally spoiled in relational land. Dynamo solves different problems, but nothing like a boring ol SQL database when you need those joins 😂
While the explanation is up to the point ! scalable database but, it sacrifices flexibility! Directly designing the ER (Entity-Relationship) for DynamoDB why invest time in learning it when it's not open-source? after few years aws might abandoned this product