◆ Amazon DynamoDB

Design DynamoDB primary and sort keys

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All Amazon DynamoDB tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskDesign the primary and sort keys for a new 'events' table. The table needs to store event…+
Design the primary and sort keys for a new 'events' table. The table needs to store event details and allow efficient lookup of all events for a specific user, as well as finding events within a date range for that user.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I commit to the primary and sort key design for the 'events' table, make sure it's…+
Before I commit to the primary and sort key design for the 'events' table, make sure it's optimized for our most critical access patterns. I need to ensure that retrieving a user's events for a specific day is lightning fast, and that the chosen keys won't lead to hot partitions as user activity scales up next quarter.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe primary key I chose for the 'events' table, using 'user_id' as the partition key, is…+
The chosen primary key for the 'events' table is causing hot partitions during peak usage.
The primary key I chose for the 'events' table, using 'user_id' as the partition key, is causing hot partitions during peak times, leading to throttling errors. The analytics team needs reliable data by Monday morning, and I can't get consistent performance. I'm not sure if I should add a prefix to the user ID or completely rethink the partition key strategy. What's the most effective way to distribute the writes more evenly, and what's the fastest fix to get the analytics team their data on time?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently underestimate the long-term impact of primary and sort key design on both…+
I frequently underestimate the impact of primary key design on scalability and cost.
I consistently underestimate the long-term impact of primary and sort key design on both scalability and cost for new DynamoDB tables. This often leads to painful re-designs or unexpected expenses down the line. What habit should I change in my initial key design process to better anticipate these issues and create more robust, cost-effective solutions from the start?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Amazon DynamoDB's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.