◆ Apache Cassandra

Plan capacity for 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 taskPlan the capacity for our user authentication database. We expect 10,000 new users per day and…+
Plan the capacity for our user authentication database. We expect 10,000 new users per day and 100,000 logins per hour during peak times. Each user record is about 1KB.
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 capacity plan for user authentication, make sure it accounts for seasonal…+
Before I finalize the capacity plan for user authentication, make sure it accounts for seasonal spikes and potential growth over the next year. Consider the impact of read-heavy versus write-heavy operations and data replication strategies.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentWe're seeing increasing latency on user login during peak hours, and the operations team is…+
We're seeing increasing latency on user login during peak hours, and the operations team is worried about running out of disk space within six months.
We're seeing increasing latency on user login during peak hours, and the operations team is worried about running out of disk space within six months, but I can't tell if it's a read or write bottleneck, or just insufficient storage. I'm afraid of recommending an expensive cluster expansion that doesn't solve the real problem. What's the likely diagnosis and what's the best next move to accurately assess and address the capacity issue?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep losing time and credibility because I consistently underestimate the growth rate of data…+
I consistently underestimate the growth rate of data and traffic, leading to reactive capacity expansions and performance issues.
I keep losing time and credibility because I consistently underestimate the growth rate of data and traffic, leading to reactive capacity expansions and performance issues. What habit should I change to better forecast future database capacity needs, especially when initial projections are often conservative and don't account for organic viral growth?
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.