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.