◆ Apache Cassandra

Create and manage 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 new keyspace named 'customer_data' with a replication factor of 3 and a…+
Create a new keyspace named 'customer_data' with a replication factor of 3 and a NetworkTopologyStrategy. Then, define a table 'users' inside it with columns for 'user_id' (UUID primary key), 'username' (text), 'email' (text), and 'created_date' (timestamp).
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 this schema for the new user activity log, make sure it performs well under…+
Before I finalize this schema for the new user activity log, make sure it performs well under high write load. Suggest the optimal primary key for querying by user and time, and consider if any clustering columns need secondary indexes to avoid slow lookups for specific event types.
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 dashboard queries are timing out on the 'events_by_user' table, especially…+
The new analytics dashboard queries are timing out on the 'events_by_user' table.
The new analytics dashboard queries are timing out on the 'events_by_user' table, especially for users with lots of activity. I designed the primary key to be (user_id, event_time) and I'm worried about hot partitions. We have a demo for the VP on Friday. Is this a data modeling issue or a query pattern problem? What's the fastest way to get these dashboard queries working reliably by end of day?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep having to refactor data models weeks after initial deployment due to performance issues…+
I keep having to refactor data models weeks after initial deployment due to performance issues.
I keep having to refactor data models weeks after initial deployment due to performance issues that only show up under production load. I'm losing too much time and credibility with the product team. What habit should I change in my data modeling process to better anticipate access patterns and avoid these costly reworks?
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.