NoSQL
NoSQL: Model access patterns and consistency needs for nonrelational data. Review schemas, data lineage, row grain, volumes, freshness, and downstream consumers and produce a NoSQL schema and query plan.
--- name: data-databases-nosql description: Use for nosql when asked to model access patterns and consistency needs for nonrelational data; produce a NoSQL schema and query plan. license: MIT metadata: author: Thrive category: data-databases --- # NoSQL ## When to use Use this skill for nosql when you need to model access patterns and consistency needs for nonrelational data. The expected result is a NoSQL schema and query plan. ## Boundaries Work within the requested task and its stated acceptance criteria. Drafting an artifact does not authorize publishing it, spending funds, changing a live system, or contacting another person. Identify any such action separately before taking it. ## Inputs Inspect schemas, data lineage, row grain, volumes, freshness, and downstream consumers. Resolve missing information that would change the method; state lesser assumptions in the result. ## Method 1. **Diagnose.** Map tables or collections, keys, row grain, indexes, volumes, consumers, and expected freshness. 2. **Decide.** Choose a transformation or storage design that preserves contracts and can be replayed. 3. **Produce.** Build a NoSQL schema and query plan from the inspected material; keep assumptions distinguishable from observed facts. ## Decision rules - Specify nulls, duplicates, late data, schema drift, and replay behavior before transformation or migration. - When sources or constraints conflict, record the conflict and choose the path supported by the user's goal and the strongest available evidence. If neither path can be supported, identify the missing decision before changing the artifact. ## Domain rules - Define null, duplicate, late-arrival, and deletion behavior. - Document migration, backfill, and rollback expectations. ## Verification Check hot keys, index use, and consistency trade-offs. Compare the result with the user's acceptance criteria and record any unverified boundary. Reconcile sample and aggregate results; include query plan or pipeline metrics and rollback or backfill steps. ## Stop conditions If a material input, required authorization, or a safe way to verify the result is absent, stop the affected action. Return the specific blocker and the smallest fact or decision needed to continue. Do not report an unrun check as passed. ## Output Provide a NoSQL schema and query plan. Include the decisive evidence and actual verification result. Name any artifact location and unresolved issue that affects its use. <!-- MIT License Copyright (c) 2026 Thrive Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -->