◆ Amazon DynamoDB

Design DynamoDB tables

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 taskCreate a new DynamoDB table named 'product_catalog' with 'product_id' as the primary key and…+
Create a new DynamoDB table named 'product_catalog' with 'product_id' as the primary key and 'category' as a sort key. Ensure it's configured for on-demand capacity.
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 acceptWe're designing a new table for managing user sessions. It needs to support frequent lookups by…+
We're designing a new table for managing user sessions. It needs to support frequent lookups by 'session_id' and also allow efficient querying of all active sessions for a given 'user_id'. Propose a table design that optimizes for both these access patterns and handles high write volume during peak hours.
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 team is split on the primary key design for our new 'order_history' table. Some want…+
The team is split on the primary key design for our new 'order_history' table.
The team is split on the primary key design for our new 'order_history' table. Some want 'order_id' as the partition key, others 'customer_id' with 'order_date' as a sort key. We anticipate high volume lookups by order_id, but also need to quickly retrieve all orders for a customer. I’m worried about hot partitions if we pick the wrong one, and the cost implications for secondary indexes. What's the best approach here to balance performance and cost, and what are the trade-offs I'm not seeing?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often find myself redesigning tables or adding new indexes after launch because of unforeseen…+
I often find myself redesigning tables or adding new indexes after launch because of unforeseen access patterns.
I often find myself redesigning tables or adding new indexes after launch because of unforeseen access patterns, leading to delays and rework. This impacts our sprint velocity and credibility with product. What habit should I change in my table design process to better anticipate future needs and create more resilient, future-proof schemas 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.