◆ Apache Cassandra

Implement Cassandra replication

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 taskConfigure a replication factor of 3 for the 'customer_data' keyspace across all three data…+
Configure a replication factor of 3 for the 'customer_data' keyspace across all three data centers and confirm all existing data is consistent within the next 30 minutes.
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 onboard the new region's users next month, review the current replication strategy…+
Before we onboard the new region's users next month, review the current replication strategy for the 'user_profiles' keyspace. Suggest improvements to ensure high availability and data durability without significantly increasing storage costs.
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 just lost a data center, and I'm seeing inconsistent data in the 'transaction_logs'…+
We just lost a data center, and I'm seeing inconsistent data in the 'transaction_logs' keyspace.
We just lost a data center, and I'm seeing inconsistent data in the 'transaction_logs' keyspace. I'm afraid we might have data loss or corruption, and I don't know if our current replication settings are robust enough. What's the most likely reason for this inconsistency, and what's the best next step to restore full data consistency and ensure no transactions are lost?
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 find myself scrambling to re-sync data or explain inconsistencies after node failures…+
I often find myself scrambling to re-sync data or explain inconsistencies after node failures.
I often find myself scrambling to re-sync data or explain inconsistencies after node failures because I'm always reacting to replication issues. What habit should I change to proactively ensure our replication strategy is always robust and validated, minimizing data loss risk and recovery time?
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.