database-selection
/database-selection
Database selection: PostgreSQL as default, Redis for ephemeral, NoSQL comparison, specialized databases, polyglot persistence. Use when choosing databases.
- Author
- rnavarych ↗
- Repository
- alpha-engineer ↗
- Licence
- MIT
- Last repository change
- 24.07.2026
Assessment and security
- Files in this package
- 7
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/analyze-data-model.sh
What it does and when to use it
Database selection: PostgreSQL as default, Redis for ephemeral, NoSQL comparison, specialized databases, polyglot persistence. Use when choosing databases.
Original author description
Database selection: PostgreSQL as default, Redis for ephemeral, NoSQL comparison, specialized databases, polyglot persistence. Use when choosing databases.
How it works
- When to use
- Core principles
- References available
- Scripts available
- Assets available
SKILL.md preview
--- name: database-selection description: | Database selection: PostgreSQL as default, Redis for ephemeral, NoSQL comparison, specialized databases, polyglot persistence. Use when choosing databases. allowed-tools: Read, Grep, Glob --- # Database Selection ## When to use - Choosing primary database for a new service - Adding a specialized database (cache, search, analytics, time-series) - Evaluating polyglot persistence or multi-database architecture ## Core principles 1. **PostgreSQL is the default** — handles 10k TPS, JSONB, full-text search, extensions 2. **Add databases for specific access patterns** — not because it's trendy 3. **Every additional database doubles operational complexity** — worth it only for clear ROI 4. **Consistency model is a product decision** — strong vs eventual affects user experience 5. **Benchmark with YOUR data** — vendor benchmarks are meaningless for your workload ## References available - `references/relational-comparison.md` — Postgres vs MySQL vs SQLite vs CockroachDB - `references/nosql-comparison.md` — MongoDB vs DynamoDB vs Cassandra vs Redis use cases - `references/specialized-databases.md` — TimescaleDB, Neo4j, Pinecone, pgvector, Elasticsearch - `references/multi-database-patterns.md` — polyglot persistence, CQRS stores, data sync ## Scripts available - `scripts/analyze-data-model.sh` — reads schema/migration files to suggest database fit ## Assets available - `assets/database-decision-matrix.md` — fillable template: requirements → recommendation
Files in this package (7)
- SKILL.md 2 KB
- assets/database-decision-matrix.md 3 KB
- references/multi-database-patterns.md 6 KB
- references/nosql-comparison.md 5 KB
- references/relational-comparison.md 4 KB
- references/specialized-databases.md 5 KB
- scripts/analyze-data-model.sh 6 KB
Versions
The database has no other skills named database-selection.
Database snapshot: 13.11.2026 · package version 47068211fda2 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100database-design
Database schema design, optimization, and migration patterns for PostgreSQL, MySQL, and NoSQL databases. Use for designing schemas, writing migrations, or optimizing queries. - 95database-expert
Advanced database design and administration for PostgreSQL, MongoDB, and Redis. Use when designing schemas, optimizing queries, managing database performance, or implementing data patterns. - 90database-design-patterns
Database schema design patterns and optimization strategies for relational and NoSQL databases. Use when designing database schemas, optimizing query performance, or implementing data persistence layers at scale. - 100database-designer
Use when the user asks to design database schemas, plan data migrations, optimize queries, choose between SQL and NoSQL, or model data relationships. - 100database-engine-implementation
Guide for implementing database engines in IterableData. Use when adding support for new SQL or NoSQL databases, implementing DBDriver classes, or extending database capabilities. - 90database-engineer
Database architecture design, schema optimization, query performance tuning, and data migration. Handles PostgreSQL, MySQL, MongoDB, Redis. Use when user asks to design database, optimize queries, create migrations, or improve database performance. Do NOT use for frontend or application logic.