◆ Apache Cassandra

Optimize Cassandra operations at scale

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskIncrease the read_repair_chance for the 'user_sessions' table in the 'analytics' keyspace to…+
Increase the read_repair_chance for the 'user_sessions' table in the 'analytics' keyspace to 0.1 and apply it to all nodes in the 'us-east-1' datacenter.
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 optimize the Cassandra cluster for the upcoming Black Friday traffic, analyze the…+
Before I optimize the Cassandra cluster for the upcoming Black Friday traffic, analyze the current read/write patterns for the 'customer_data' keyspace and identify any tables with high contention or inefficient queries that could cause bottlenecks at 5x current load.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur Cassandra cluster is experiencing high latency during peak hours, but CPU and disk I/O…+
Our Cassandra cluster is experiencing high latency during peak hours, but CPU and disk I/O look normal.
Our Cassandra cluster is experiencing high latency during peak hours, but CPU and disk I/O metrics look normal across all nodes. I'm worried this indicates a subtle configuration issue or a specific query pattern that's inefficient at scale, potentially leading to a full outage. Could it be a GC pause issue or a materialized view causing problems? What's the best immediate action to take to identify the root cause without impacting the live service?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe frequently hit performance ceilings with our distributed database whenever our traffic…+
We frequently hit performance ceilings with Cassandra whenever our traffic spikes unexpectedly.
We frequently hit performance ceilings with our distributed database whenever our traffic spikes unexpectedly, leading to customer complaints and frantic firefighting. This reactive approach is unsustainable. What habit should I change to proactively identify and address potential scaling bottlenecks in our database operations before they impact our users, rather than waiting for an incident?
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.