◆ Amazon DynamoDB

Tune DynamoDB for 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 taskOptimize the 'session_data' DynamoDB table for faster reads. Create a Global Secondary Index on…+
Optimize the 'session_data' DynamoDB table for faster reads. Create a Global Secondary Index on 'user_id' so the user profile page loads quicker for our customers.
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 the new analytics dashboard goes live, I need to tune the 'event_logs' DynamoDB table.…+
Before the new analytics dashboard goes live, I need to tune the 'event_logs' DynamoDB table. Make sure queries for specific date ranges and event types are fast, so the marketing team gets real-time insights without delay.
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 'user_preferences' service is experiencing slow query times, and the product manager is…+
The 'user_preferences' service is experiencing slow query times, delaying page loads.
The 'user_preferences' service is experiencing slow query times, and the product manager is getting impatient about the delayed page loads. We added a new query pattern last week, and I'm not sure if our existing indexes are optimized for it or if the data model itself is inefficient for these new access patterns. What's the best next step to diagnose the performance bottleneck and improve query speed quickly?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe consistently struggle with slow query performance on new features, leading to project delays…+
We consistently struggle with slow query performance on new features.
We consistently struggle with slow query performance on new features, leading to project delays and user frustration. It feels like we're always retrofitting indexes. What habit should I change in our development process to ensure we design for optimal database performance from the start, rather than fixing it later?
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.