◆ Apache Cassandra

Model data for Cassandra databases

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 Cassandra table named 'user_sessions' in the 'app_data' keyspace. It needs columns…+
Create a new Cassandra table named 'user_sessions' in the 'app_data' keyspace. It needs columns for 'session_id' (UUID, primary key), 'user_id' (text), 'login_time' (timestamp), and 'ip_address' (inet). Ensure 'user_id' can be used for efficient lookups.
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 'product_catalog' table, I need to make sure our queries for…+
Before I finalize the 'product_catalog' table, I need to make sure our queries for 'products_by_category' and 'products_by_supplier' are fast without full table scans. Right now, it's just a single primary key. What's the best way to structure the primary key and clustering columns to support these access patterns efficiently?
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 'transaction_history' table we just deployed is killing our latency for customer lookups.…+
Our new 'transaction_history' table is performing terribly for queries by 'customer_id' and 'transaction_date', even though we have those in the primary key.
The 'transaction_history' table we just deployed is killing our latency for customer lookups. We put 'customer_id' and 'transaction_date' in the primary key, thinking that would be enough, but every query is still crawling. I'm afraid we've fundamentally misunderstood how to model for our access patterns here, and I can't tell if it's the partitioning or the clustering that's wrong. What's the most likely misstep, and what's the fastest way to diagnose it without taking the system offline?
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 having to refactor Cassandra table schemas shortly after they go live because we…+
I keep having to rework Cassandra table schemas weeks after deployment because of unforeseen query patterns or performance bottlenecks.
I'm constantly having to refactor Cassandra table schemas shortly after they go live because we hit unexpected performance walls or new access patterns emerge. It's burning a lot of time and delaying features. What habit should I change in my initial data modeling process to anticipate these issues better and build more resilient schemas from the start?
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.