nslog

Have you seen my stapler?

This is a great talk. More technical videos should be done from the basics like this.

Didn't react just have basically the same vuln

This is spot on. Parts of Amplify are aimed at people just getting started with Cloud and Programming, which is good and bad. You can shoot yourself in the foot if you drive the car too fast. I think a lot of more advanced people use Amplify services along with the Amplify client SDKs and then do the provisioning using CDK rather than the Amplify CLI.

Eh their documentation is pretty clear about all this stuff and all the new directives released a couple years back (like the PK and index stuff) clearly guide people towards using indexed queries and not scans: https://docs.amplify.aws/cli/graphql/data-modeling/

A lot of this is on the author IMO

Stopped reading when this guy started talking about Single Table DDB being best practice and linking to AWS when he clearly did zero research on AWS recommendations with GraphQL including from the AWS Hero Alex Debrie he mentions: https://www.alexdebrie.com/posts/dynamodb-graphql/ https://aws.amazon.com/blogs/mobile/single-table-vs-multi-ta... https://aws.amazon.com/blogs/mobile/enhancing-dynamodb-singl...

Also he mentions the race condition around clients connecting to the backend between queries and mutations, then in the same breath says the DataStore client handles this but also it's mistake is being reliant on Subscriptions? This contradiction doesn't make sense.

There are some legit bugs in this article though that I've seen, like that Analytics one. It's really a Pinpoint issue though when you dig under the covers that I've been waiting for them to solve for years.

Finally

https://aws.amazon.com/solutions/case-studies/neimanmarcus-c... https://aws.amazon.com/solutions/case-studies/amazonmusic-am...