◆ Apache Cassandra

Apply Cassandra best practices in production

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 taskEnsure the 'user_activity' keyspace has a replication factor of 3 and uses…+
Ensure the 'user_activity' keyspace has a replication factor of 3 and uses 'NetworkTopologyStrategy' for our production environment.
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 push the new 'event_logs' service to production, I need to make sure its data storage…+
Before we push the new 'event_logs' service to production, I need to make sure its data storage usage follows our best practices. I'm particularly concerned about schema design for time-series data, proper consistency levels for writes, and efficient queries for analytical reporting. Help me review the proposed implementation against our production standards and flag any deviations that could lead to performance or operational issues.
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 new junior developer just pushed a schema change to 'product_inventory' that added an…+
The new junior developer just pushed a schema change to 'product_inventory' that added an unindexed column and used 'ALL' consistency for reads.
The new junior developer just pushed a schema change to 'product_inventory' that added an unindexed column and used 'ALL' consistency for reads. I'm afraid this will cause massive performance problems and potentially data unavailability, and I can't let it sit there. What's the likely immediate impact, and what's the best next move to revert or mitigate this without disrupting the entire system?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often discover deviations from best practices only after they cause a production incident or…+
I often discover deviations from best practices only after they cause a production incident or performance degradation.
I often discover deviations from best practices only after they cause a production incident or performance degradation, leading to urgent fixes and post-mortems. I need to embed best practices earlier in the development lifecycle. What habit should I change to ensure our team consistently applies data storage best practices in production, preventing issues before they arise?
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.