◆ Amazon DynamoDB

Use auto increment for primary key

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 taskWhen a new order comes in, add it to the 'orders' table. It needs an order ID, customer ID…+
When a new order comes in, add it to the 'orders' table. It needs an order ID, customer ID 'cust123', and a total amount of 49.99. The order ID should be a new, unique, sequential number.
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 acceptFor every new item added to the 'products' table, I need the 'product_id' to automatically…+
For every new item added to the 'products' table, I need the 'product_id' to automatically increment. Also, ensure there's a 'version' attribute that starts at 1 and increments on every update, so we can track changes easily.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentWe're using a counter table for auto-incrementing session IDs, but it occasionally throws a…+
We're trying to use auto-incrementing IDs for our 'sessions' table, but sometimes we get duplicate IDs or errors.
We're using a counter table for auto-incrementing session IDs, but it occasionally throws a 'ConditionalCheckFailedException' when multiple users try to create sessions simultaneously. I'm worried we're losing session data or creating duplicate IDs. Is this the right pattern for high-concurrency auto-increment, or is there a more robust way to guarantee unique, sequential IDs without contention?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep running into issues with ID generation, either performance bottlenecks with high…+
I frequently struggle with generating unique, sequential IDs efficiently and reliably for new records.
I keep running into issues with ID generation, either performance bottlenecks with high concurrency or accidental collisions, especially for critical tables like 'transactions'. What habit should I change to consistently implement reliable, unique, and performant primary key generation strategies without having to re-architect every time requirements scale?
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.