One of the things that I hear about single table design is that you need to understand all your access patterns up front. But rarely do requirements come up front. Agile (putting aside the cargo cult) is often executed in a way that reacts to changing demands and this seems to be an admission of flawed requirements, or information that only comes later. With the extra cognitive load of planning a single table design I feel like it’s going to optimise RCU at the cost of refactoring exercises down the track. But I’d be happy to understand opposing points of view. More on reddit.com

Partiql is meh to begin with. You're better off writing scripts to work with your entities that use the actual apis for your access patterns. More on reddit.com

Great read! I like the clarification that Amazon used the “single table design” phrase as a way to encourage teams to take a fresh look at data modeling possibilities, rather than a hard internal mandate when moving to DynamoDB More on reddit.com

You may need to store separate document. What your minimal timeframe? A day? Lets add new doc for every req update. PK = ISODate SK = reqs#object_id ttl = now() + 1 day // free deletion unused data If object was requested 2 times in a day - there will be two doc So every day you need to calculate yesterday TOP 100, (1000, 10 000 - depends on your use case) and store it in third document (max 400kb). Do not forget to deduplicate by object_id. PK = TOP#DAY#ISODate SK = TOP#DAY#ISODate id1: reqs // max id2: reqs For month it will be batch read, for year it will be a problem. But anyway there is a good news. Data in the past do not change. So you can calculate weeks, month PK = TOP#WEEK#... , TOP#MONTH#... More on reddit.com