◆ Apache Cassandra

Design a Cassandra data model

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 Apache Cassandra tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskDesign a database data model for storing customer order information, including customer ID,…+
Design a database data model for storing customer order information, including customer ID, order ID, order date, and a list of items with quantity and price.
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 finalizing this data model for customer orders, consider how the sales team will most…+
Before finalizing this data model for customer orders, consider how the sales team will most frequently query this data. They need to quickly see all orders for a specific customer, and also identify recent orders across all customers. Ensure the model supports these access patterns efficiently without creating hotspots or excessive read amplification.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI've designed a data model for product reviews, with a primary key on 'product_id' and…+
I've designed a data model for product reviews, but I'm worried about performance for aggregate queries.
I've designed a data model for product reviews, with a primary key on 'product_id' and 'review_id'. The product manager now wants to frequently query the average rating for a product and the total number of reviews. I'm afraid my current design will require full table scans or complex client-side aggregation, which will be slow and impact the real-time analytics dashboard. What's the best way to modify this model to efficiently support these aggregate queries without compromising the primary access pattern of fetching reviews by product?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently design database data models based on initial requirements, only to find myself…+
I consistently design data models that require re-work when new query patterns emerge from stakeholders.
I frequently design database data models based on initial requirements, only to find myself re-architecting them weeks later when the product team or business analysts identify new, critical query patterns. This costs us significant time and delays feature releases. How can I change my habit to anticipate future access patterns and design more flexible, scalable data models from the outset, reducing the need for costly re-work and improving our credibility?
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 Apache Cassandra'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.