◆ Amazon DynamoDB

Optimize DynamoDB query and scan performance

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskThe 'product_catalog' service is experiencing slow response times. I need to optimize the query…+
The 'product_catalog' service is experiencing slow response times. I need to optimize the query for fetching product details by category to speed it up.
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 our next marketing push, I need to improve the performance of our 'customer_history'…+
Before our next marketing push, I need to improve the performance of our 'customer_history' service's queries. Help me analyze the current access patterns and suggest index changes or query modifications to ensure quick retrieval of customer order history without hitting throttling limits.
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 'recommendation_engine' is performing terribly during peak hours, and I strongly suspect…+
Our 'recommendation_engine' is performing poorly during peak hours, and I suspect it's a full table scan that's killing us.
The 'recommendation_engine' is performing terribly during peak hours, and I strongly suspect it's a full table scan on our 'user_preferences' table, but I can't immediately see which query is doing it. I'm afraid of adding an index that might slow down writes, and I need to fix this before the weekend. What's the most likely culprit for this slowdown, and what's the safest first step to confirm it and improve performance without impacting other critical operations?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly reacting to slow queries and scans reported by users or monitoring, often after…+
I frequently find myself optimizing queries only after they've already caused performance degradation for users.
I'm constantly reacting to slow queries and scans reported by users or monitoring, often after they've already impacted customer experience. It feels like I'm always playing catch-up. What habit should I change to proactively identify and optimize inefficient queries and scans before they become a problem in production, especially for new features or evolving access patterns?
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.