◆ Apache Cassandra

Design software solutions

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 taskUpdate the Cassandra schema for the 'product_catalog' table to add a new 'last_updated_by'…+
Update the Cassandra schema for the 'product_catalog' table to add a new 'last_updated_by' column of type text. Ensure the change is non-disruptive to existing data.
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 design for the new customer analytics platform, make sure the data model…+
Before I finalize the design for the new customer analytics platform, make sure the data model supports flexible queries for future reporting. Consider how new dimensions like 'customer_segment' or 'purchase_frequency' could be added without requiring major schema rewrites, and anticipate potential read/write hotspots.
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 real-time recommendation engine is hitting severe latency spikes, and the Cassandra…+
The new real-time recommendation engine is experiencing unacceptable latency spikes, and the Cassandra cluster's CPU utilization is through the roof.
The new real-time recommendation engine is hitting severe latency spikes, and the Cassandra cluster's CPU is maxed out. I designed the data model for high throughput, but these specific queries are hammering a single partition key. If I don't fix this, the product launch will be a disaster, but changing the data model now means a huge refactor. I can't just throw more hardware at it; we're already over budget. What's the core problem causing these performance issues, and what's the most effective immediate action to mitigate the latency without a full data model redesign?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternMy initial data model designs often look good on paper but then struggle with performance or…+
I frequently find my initial Cassandra data model designs don't scale or perform as expected once under real production load.
My initial data model designs often look good on paper but then struggle with performance or scalability once they hit production, leading to painful redesigns and data migrations. It feels like I'm missing something fundamental during the planning phase. What habit should I change in my design process to anticipate real-world access patterns and data growth more accurately, so my solutions are robust from day one?
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.