nosql-expert

Guide distributed NoSQL database design for Cassandra and DynamoDB with query-first modeling.

2|Updated Feb 6, 2026

Search Tags:#performance #database design #scalability #data modeling #nosql #dynamodb #cassandra

Ready to run

npx skills add https://github.com/bcastelino/agent-skills-kit --skill nosql-expert

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nosql-expert
Source: https://github.com/bcastelino/agent-skills-kit/tree/main/skills/nosql-expert
Command: npx skills add https://github.com/bcastelino/agent-skills-kit --skill nosql-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides expert guidance for designing and optimizing distributed NoSQL databases like Cassandra and DynamoDB, focusing on high-scale data modeling and performance.

Core Features & Use Cases

Query-First Modeling: Learn to design schemas around access patterns, not just entities.
Partition Key Strategy: Understand how to avoid hot partitions for even data distribution and throughput.
Single-Table Design: Implement efficient data retrieval patterns, especially for DynamoDB.
Use Case: You are designing a new microservice that requires a highly scalable database. Use this Skill to ensure your Cassandra or DynamoDB schema is optimized for read performance and avoids common pitfalls like hot partitions.

Quick Start

Explain the concept of a partition key in DynamoDB and how to choose a good one.

Frequently Asked Questions about nosql-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I design a DynamoDB schema using query-first modeling?▼

DynamoDB query-first modeling designs schemas around application access patterns rather than entities, enabling efficient single-table data retrieval and optimized read performance for high-scale distributed systems.

What is a partition key in DynamoDB and how do I avoid hot partitions?▼

A DynamoDB partition key distributes data across storage partitions. Avoid hot partitions by selecting high-cardinality partition keys that evenly distribute read and write throughput, preventing concentrated traffic bottlenecks.

When should I use single-table design patterns for NoSQL databases?▼

Use NoSQL single-table design patterns when retrieving multiple related entity types in a single query, maximizing read performance and minimizing latency in highly scalable distributed database architectures.

How do I optimize Cassandra data modeling for high-scale system performance?▼

Optimize Cassandra data modeling by prioritizing query-first design, selecting appropriate partition keys to prevent hot partitions, and structuring schemas to ensure even data distribution and throughput across cluster nodes.

What are the limitations of single-table design in distributed NoSQL databases?▼

Single-table design in distributed NoSQL databases introduces schema complexity, requires deep upfront knowledge of all access patterns, and complicates ad-hoc querying, making future schema modifications difficult without data migration.