◆ Amazon DynamoDB

Calculate Read/Write Capacity Units

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 taskCalculate the Read Capacity Units and Write Capacity Units for the 'sessions' table, assuming…+
Calculate the Read Capacity Units and Write Capacity Units for the 'sessions' table, assuming 100 reads per second and 20 writes per second, with an average item size of 1KB.
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 we launch the new user activity feed, figure out the optimal Read/Write Capacity Units…+
Before we launch the new user activity feed, figure out the optimal Read/Write Capacity Units for the 'activity_log' table. Consider the expected peak traffic of 500 reads and 150 writes per second, and account for the 2KB average item size, ensuring we don't overprovision but also avoid throttling.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur 'notifications' table is hitting throttling errors every afternoon, but I can't pinpoint if…+
The 'notifications' table is getting throttled during peak hours, but I'm unsure if it's reads or writes, or if the item size is the issue.
Our 'notifications' table is hitting throttling errors every afternoon, but I can't pinpoint if it's a sudden spike in reads or writes, or if the average item size has unexpectedly grown. I'm afraid of increasing capacity blindly and wasting budget. How do I diagnose the exact cause of the throttling and determine the right capacity adjustment?
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 underestimating or overestimating the capacity for new tables, which either leads to…+
I consistently struggle to accurately estimate capacity for new tables, leading to either overspending or performance issues.
I keep underestimating or overestimating the capacity for new tables, which either leads to painful throttling during load tests or unnecessary costs. I spend too much time tweaking after deployment. What habit should I change to get better at predicting Read/Write Capacity Units more accurately 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.