◆ Apache Cassandra

Provide Apache Cassandra support services

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 taskGenerate a report for the 'finance_reporting' keyspace showing its current replication factor,…+
Generate a report for the 'finance_reporting' keyspace showing its current replication factor, consistency level, and schema definition, then email it to Sarah in finance and Mark in compliance by end of day.
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 provide a detailed support plan for the new 'inventory_management' application's…+
Before I provide a detailed support plan for the new 'inventory_management' application's database usage, give me a summary of best practices for data modeling and query design that will ensure high availability and data integrity for a critical operational system, considering our current cluster setup.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA new developer just deployed a service that's hammering our distributed database with…+
A new developer just deployed a service that's hammering Cassandra with unoptimized queries, causing cluster-wide latency spikes.
A new developer just deployed a service that's hammering our distributed database with unoptimized queries, causing cluster-wide latency spikes. I'm afraid of a full production outage if this continues, but I don't want to directly blame them or cause friction. Is it better to immediately roll back their deployment, or try to identify and throttle the problematic queries first? What's the most diplomatic and effective next step to stabilize the cluster and prevent future occurrences?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI constantly find myself reacting to database issues that could have been prevented with better…+
I constantly find myself reacting to Cassandra issues that could have been prevented with better initial design or communication.
I constantly find myself reacting to database issues that could have been prevented with better initial design or communication from application teams. This reactive work drains my time and energy. What habit should I change to embed better database practices earlier in the development lifecycle, ensuring new services don't inadvertently create problems for the cluster or other teams?
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.