◆ Amazon DynamoDB

Model relational data in DynamoDB

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 taskModel the 'products', 'categories', and 'product_categories' relational data within a single…+
Model the 'products', 'categories', and 'product_categories' relational data within a single DynamoDB table, ensuring that I can query products by category and retrieve all categories for a given product efficiently for the new e-commerce catalog.
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 I finalize the single-table design for products and categories, make sure it's…+
Before I finalize the single-table design for products and categories, make sure it's future-proof for our growth. I need to anticipate how we'll handle new attributes for products or categories without requiring a full data migration, and ensure that read-heavy category browsing remains performant as the catalog expands.
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 single-table design for products and categories is turning into a nightmare for new…+
The single-table design for products and categories is becoming too complex for new features.
The single-table design for products and categories is turning into a nightmare for new features; adding a simple 'brand' attribute to products or a 'seasonal' flag to categories requires modifying multiple item types and access patterns. Mark from product wants to add discounts by brand next week. I'm afraid of introducing bugs with every change. What's the best way to simplify this design without a full re-architecture, and what's the immediate next step to support the new brand feature?
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 struggle to find the right balance between optimizing for specific query patterns and…+
I frequently struggle with balancing query efficiency and data flexibility in single-table designs.
I often struggle to find the right balance between optimizing for specific query patterns and maintaining data flexibility when modeling relational data in a single DynamoDB table. This leads to designs that are either too rigid or too inefficient. What habit should I change in my initial data modeling approach to better anticipate future access patterns and attribute growth without compromising performance?
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.