◆ Apache Cassandra

Determine Cassandra hardware requirements

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.

2prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AImprove — make it easier to acceptBefore I present this hardware proposal for the new analytics cluster, make sure it's resilient…+
Before I present this hardware proposal for the new analytics cluster, make sure it's resilient and cost-effective. Highlight any potential bottlenecks for our projected growth over the next year and suggest alternative instance types if there's a better balance of performance and cost.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BDecide — diagnose the stuck momentFinance just slashed our proposed hardware budget for the new reporting cluster by 30%. We need…+
The finance team just cut our proposed budget for the new Cassandra cluster by 30%.
Finance just slashed our proposed hardware budget for the new reporting cluster by 30%. We need to support 8,000 writes/sec and 4,000 reads/sec, with 2TB of data, replication factor 3. I'm afraid of under-provisioning and hitting performance walls immediately. What's the most critical component to scale back on first to meet the budget while minimizing performance impact, and what's the minimum viable configuration I can propose to still meet the core requirements?
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.