Do you think I'm a liar? 🤔

Thanks for flagging that, fixed it.

All your entities in one table is "recommended", by who? DynamoDB does not recommend this, we recommend you store data that you want to read in a single request be stored in a single table. Otherwise, having a table per entity is recommended as it reduces complexity.

You can't change the keys on an existing table. But you can easily use ExportToS3 and then use ImportFromS3 and define the schema with the new keys.

Just be sure that your newly keyed schema has uniqueness throughout your entire data.

😂 keep at it, I find it difficult to use SQL syntax now, I far prefer the more strict restful approach.

If you need any info on DynamoDB, feel free to reach out.

The Query syntax is relatively simple once you give it a try. Use a high level SDK that can abstract the DDB-JSON for you, it'll resonate much easier for you then. Feel free to reach out if you need any help.

The 10GB limit only comes into play if you use an LSI, having an LSI prevents partitions from splitting item collections as it needs to keep the index consistent on the same node. GSI is much more flexible and doesn't impose a limit on partition keys, although it only offers eventually consistency.

There is no 10GB limit per key in DynamoDB.

Which DynamoDB 10GB limit?

What’s the trickiest scaling challenge you’ve faced with DynamoDB? Let’s discuss!

#NoSQL #DynamoDB

4. ✅ Check for efficient queries: avoid large scans or pagination overhead.

docs.aws.amazon.com/amazondynamo...

3. ✅ Pre-warm your table using warm throughput to make sure your table or index is ready for your peak load.

aws.amazon.com/blogs/databa...

2. ✅ Design with access patterns in mind to reduce throttling.

docs.aws.amazon.com/amazondynamo...

1. ✅ Use partition keys that distribute load evenly (no hot keys).

docs.aws.amazon.com/amazondynamo...