Agent skill · research science · aiskillstore
nosql-expert
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.
Why this skill is useful
Provides domain-specific knowledge on NoSQL design patterns and query-first modeling that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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. Core Design Patterns 1. Query-First Modeling (Access Patterns) You typically cannot "add a query later" without migration or creating a new table/index. Process: 1. List all Entities (User, Order, Product). 2. List all Access Patterns ("Get User by Email", "Get Orders by User sorted by Date"). 3. Design Table(s) specifically to serve those patterns with a single lookup. 2. The Partition Key is King Data is distributed across physical nodes based on the Partition Key (PK). Goal: Even distribution of data and traffic. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/nosql-expert