nosql-expert

Guide NoSQL data model design around access patterns for Cassandra and DynamoDB.

6|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/ChrstprJohn/SamsonDentalCenter --skill nosql-expert-chrstprjohn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nosql-expert
Source: https://github.com/ChrstprJohn/SamsonDentalCenter/tree/main/.agent/skills/nosql-expert
Command: npx skills add https://github.com/ChrstprJohn/SamsonDentalCenter --skill nosql-expert-chrstprjohn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

NoSQL design often forces you to optimize for specific queries rather than data entities; this skill teaches you to model around access patterns to achieve scalable, predictable performance.

Core Features & Use Cases

  • Query-First Modeling (Access Patterns)
  • The Partition Key is King
  • Clustering / Sort Keys
  • Single-Table Design (Adjacency Lists)
  • Denormalization & Duplication Use cases include designing tables for user profiles, orders, and events in Cassandra or DynamoDB, with strategies to avoid hot partitions and to support efficient reads.

Quick Start

List your application's primary access patterns and translate them into table designs that serve these patterns with minimal lookups.

Frequently Asked Questions about nosql-expert

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

FAQPage Schema
How do I design NoSQL data models for specific queries?

NoSQL data models require a query-first approach, prioritizing access patterns over data entities to achieve scalable performance. You translate primary application queries into table designs that serve reads efficiently with minimal lookups.

What is single-table design in DynamoDB?

Single-table design is a NoSQL modeling approach using adjacency lists to structure multiple entity types within one table. It leverages partition keys and sort keys to fetch related data efficiently in a single request for query-first modeling.

How do I avoid hot partitions in Cassandra?

Avoid hot partitions in Cassandra by selecting partition keys that distribute write loads evenly across the cluster. Modeling around access patterns and applying denormalization strategies prevents uneven traffic concentration on specific nodes.

When should I use denormalization in NoSQL databases?

Use denormalization in NoSQL databases when optimizing schemas for specific access patterns and write-heavy workloads. Duplicating data across tables eliminates additional lookups and allows queries to retrieve required data efficiently.

Does this approach work for both DynamoDB and Cassandra?

Yes, the query-first modeling approach applies to distributed stores like DynamoDB and Cassandra. It covers partition keys, clustering keys, and single-table design across microservices for both platforms.

What is the best way to model write-optimized schemas for microservices?

The best way to model write-optimized schemas for microservices is applying query-first NoSQL design with single-table design and denormalization. This satisfies access patterns while avoiding hot partitions and supporting efficient reads.