◆ Apache Cassandra

Store massive ordered time series data

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 taskAdd the sensor readings for device 734 from the last hour into the 'telemetry' table, ensuring…+
Add the sensor readings for device 734 from the last hour into the 'telemetry' table, ensuring they are ordered by timestamp and partitioned by device ID.
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 ingest the new smart meter data, ensure the 'readings' table schema will handle the…+
Before we ingest the new smart meter data, ensure the 'readings' table schema will handle the expected volume and query patterns without performance degradation, especially for range queries on timestamps. Flag any potential hotspots or compaction 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 IoT fleet's data ingestion just spiked, and I'm seeing erratic read latency across the…+
The data ingestion for the new IoT fleet just spiked, and I'm seeing erratic latency on reads.
The new IoT fleet's data ingestion just spiked, and I'm seeing erratic read latency across the cluster. The monitoring shows some nodes are struggling more than others, but there's no clear pattern on disk I/O or CPU. I'm worried about data loss or a complete cluster freeze during peak hours, and I can't tell if it's a hot partition, a compaction storm, or something else entirely. What's the most likely cause, and how should I prioritize investigating this without impacting live services?
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 getting pulled into performance crises whenever a new application starts writing…+
I keep getting called in to fix performance issues on time-series data when new applications go live.
I keep getting pulled into performance crises whenever a new application starts writing time-series data, even after schema reviews. The problem always seems to be how the data is partitioned and queried at scale. What habit should I change in our initial data modeling discussions to prevent these recurring bottlenecks and ensure more resilient designs from the start?
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.