Expert guidance for distributed NoSQL databases (Cassandra, DynamoDB). Focuses on mental models, query-first modeling, single-table design, and avoiding hot partitions in high-scale systems.
NewMaintained
Automatic
◆Data Engineer pack
Last verified 8/29/2026
What it changes
Passed 0 of 23 test cases with the skill, and 23 of 23 without it.
Without skill100%
With skill0%
Checks it passed that the model alone missed
Explain that BatchGetItem retrieves up to 100 items across tables in a single network round-trip.
1 fixed21 passed either way0 still failing1 broke
Pass-rate lift
-100 pp
Tokens
+31%
Agent turns
0%
Response time
+12%
Model gemini-3.6-flashMeasured 8/29/2026v122 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
A backend service needs to fetch details for 25 distinct user records from Amazon DynamoDB, where each user record has a unique, non-sequential partition key. Developers are considering making 25 separate `GetItem` calls in a loop. What API method should be used instead to reduce network overhead?
What was checked, without and with the skill
Checked
Without skill
With skill
Recommend using the BatchGetItem API operation.
Passed
Passed
Explain that BatchGetItem retrieves up to 100 items across tables in a single network round-trip.
Missed
Passed
case-14 · gemini-3.6-flash · 8/29/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md38 linessingle file
NoSQL Expert Patterns (Cassandra & DynamoDB)
Overview
This skill provides professional mental models and design patterns for distributed wide-column and key-value stores (specifically Apache Cassandra and Amazon DynamoDB).
Unlike SQL (where you model data entities), or document stores (like MongoDB), these distributed systems require you to model your queries first.
When to Use
Designing for Scale: Moving beyond simple single-node databases to distributed clusters.
Technology Selection: Evaluating or using Cassandra, ScyllaDB, or DynamoDB.
Performance Tuning: Troubleshooting "hot partitions" or high latency in existing NoSQL systems.
Microservices: Implementing "database-per-service" patterns where highly optimized reads are required.
The Mental Shift: SQL vs. Distributed NoSQL
Feature
SQL (Relational)
Distributed NoSQL (Cassandra/DynamoDB)
Data modeling
Model Entities + Relationships
Model Queries (Access Patterns)
Joins
CPU-intensive, at read time
Pre-computed (Denormalized) at write time
Storage cost
Expensive (minimize duplication)
Cheap (duplicate data for read speed)
Consistency
ACID (Strong)
BASE (Eventual) / Tunable
Scalability
Vertical (Bigger machine)
Horizontal (More nodes/shards)
The Golden Rule: In SQL, you design the data model to answer any query. In NoSQL, you design the data model to answer specific queries efficiently.