◆ Amazon DynamoDB

Model relationships in DynamoDB

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.

3prompts
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 taskI need to model the relationships between customer accounts, their orders, and the individual…+
I need to model the relationships between customer accounts, their orders, and the individual items within each order. Each order item needs to reference its parent order, and orders need to reference their customer. This is for the new order processing service.
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 finalize this data model for customer orders, make sure it optimizes for the most…+
Before I finalize this data model for customer orders, make sure it optimizes for the most common access patterns: retrieving all orders for a customer, and getting all items for a specific order. I'm worried about read performance as the system scales.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CBecome — change the patternI keep struggling to balance the immediate performance gains of a single-table design with the…+
I keep struggling to balance single-table design benefits with future query flexibility when modeling new features in DynamoDB.
I keep struggling to balance the immediate performance gains of a single-table design with the long-term flexibility needed for evolving access patterns. This often leads to rework or performance bottlenecks later. What habit should I change to better anticipate future data access needs without over-engineering every new data model?
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.