Architecture Database Selection SQL Vs Nosql

Imported TRAE skill from architecture/Database_Selection_SQL_vs_NoSQL.md Use when this capability is needed.

tomevault-io 5469062 2 files · 1.8 KB Updated

File contents

Database Selection (SQL vs NoSQL)

SQL (Relational)

  • Examples: PostgreSQL, MySQL.
  • Use Case: Structured data, complex relationships, transactions (ACID), reporting.
  • Schema: Rigid, requires migrations.

NoSQL (Non-Relational)

  • Examples: MongoDB (Document), Redis (Key-Value), Cassandra (Wide-Column).
  • Use Case: Unstructured data, high write throughput, horizontal scaling, flexible schema.
  • Schema: Flexible/Schema-less.

Selection

  • Choose SQL by default for most business applications.
  • Choose NoSQL for specific needs like caching (Redis), massive logs, or rapidly changing data structures.

Source: Ditto190/crispy-nextjs-turborepo-monorepo — distributed by TomeVault.

tomevault-io/skills-registry/tree/main/ditto190--crispy-nextjs-turborepo-monorepo--architecture-database-selection-sql-vs-nosql commit 5469062299

Frequently asked questions

npx skillmds@latest add tomevault-io/architecture-database-selection-sql-vs-nosql