◆ Apache Cassandra

Design Cassandra NoSQL 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 table named 'user_sessions' with columns for session_id, user_id, start_time,…+
Create a table named 'user_sessions' with columns for session_id, user_id, start_time, end_time, and events, where session_id is the primary key and events is a list of text.
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 we finalize the 'product_catalog' table, ensure its data model supports efficient…+
Before we finalize the 'product_catalog' table, ensure its data model supports efficient queries for products by category, by price range, and by keyword search, without requiring secondary indexes on high-cardinality columns or large partitions. Flag any design choices that could lead to hot spots or slow reads.
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 product team wants to add a new feature tracking user engagement with specific UI elements,…+
The product team wants to add a new feature that tracks user engagement with specific UI elements, but our current 'user_activity' model won't scale.
The product team wants to add a new feature tracking user engagement with specific UI elements, generating hundreds of events per user per session. Our current 'user_activity' model, partitioned by user ID, will create massive partitions for active users, leading to performance issues and compaction storms. I'm afraid of a complete system slowdown, but I can't tell if a composite partition key, a separate table, or a time-bucketed approach is best without over-complicating the application. What's the most effective data model strategy here, and what are the trade-offs?
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 find myself redesigning tables after they've gone live because of unforeseen query…+
I frequently find myself redesigning tables after they've gone live because of unforeseen query patterns or growth.
I frequently find myself redesigning tables after they've gone live because of unforeseen query patterns or data growth, leading to costly migrations and downtime. This happens even after initial discussions. What habit should I change in my data modeling process to better anticipate future access patterns and scale requirements, ensuring more robust designs 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.