◆ Apache Cassandra

Design Cassandra data models

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 taskCreate a Cassandra table called 'user_sessions' in the 'app_keyspace' with 'session_id' as the…+
Create a Cassandra table called 'user_sessions' in the 'app_keyspace' with 'session_id' as the primary key, 'user_id' as a clustering column, and columns for 'start_time' and 'end_time'.
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 acceptI need to design a new data model for customer order history. Before I commit to this, help me…+
I need to design a new data model for customer order history. Before I commit to this, help me make sure it will scale efficiently. I'm worried about hot partitions if I use 'customer_id' directly and want to avoid expensive full table scans for date ranges. Suggest a model that balances read and write performance for typical order lookups and historical reporting.
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 new analytics team just asked for a query that hits 'user_activity' by country and date…+
The new analytics team wants to query historical user activity by country and date range, but our current 'user_activity' table is partitioned by 'user_id'.
The new analytics team just asked for a query that hits 'user_activity' by country and date range, but our current model is user-centric. I'm afraid of creating a massive, slow query that crashes a node, and I can't tell them we can't do it. What's the best way to support this without a full re-architecture right now, and what are the trade-offs I should be aware of?
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 getting pulled into urgent meetings because new features need data access…+
I keep getting pulled into urgent meetings because new features require data access patterns our current models don't support well.
I'm constantly getting pulled into urgent meetings because new features need data access patterns that our existing data models don't support efficiently, leading to last-minute schema changes or performance bottlenecks. I need to get better at anticipating these future needs during the initial design phase. What habit should I change to design more resilient and forward-looking data models?
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.