database-selection

Analyze project data models and access patterns to recommend a database technology.

14|3|Updated Feb 22, 2026

Search Tags:#architecture #database #postgresql #nosql #mongodb #selection #relational

Ready to run

npx skills add https://github.com/rnavarych/alpha-engineer --skill database-selection

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: database-selection
Source: https://github.com/rnavarych/alpha-engineer/tree/main/plugins/billy-milligan/skills/architecture/database-selection
Command: npx skills add https://github.com/rnavarych/alpha-engineer --skill database-selection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps developers select the most appropriate database technology for their specific project requirements, avoiding costly mistakes and optimizing performance.

Core Features & Use Cases

Guided Selection: Provides a structured approach to database choice based on data models, access patterns, and operational needs.
Comparison: Offers insights into relational, NoSQL, time-series, graph, and vector databases.
Use Case: When starting a new microservice, use this Skill to analyze your data structure and access patterns to recommend whether PostgreSQL, MongoDB, or a specialized database like TimescaleDB or Neo4j is the best fit.

Quick Start

Use the database-selection skill to analyze my project's data model and recommend a primary database.

Frequently Asked Questions about database-selection

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

FAQPage Schema

How do I choose the right database for my project's data model and access patterns?▼

Database selection involves analyzing your project's data models, access patterns, and operational requirements to recommend the optimal technology. This structured approach evaluates relational, NoSQL, time-series, graph, and vector databases to facilitate informed decisions for new service development.

When should I use a NoSQL database like MongoDB or Cassandra instead of a relational database?▼

NoSQL databases like MongoDB, Cassandra, or DynamoDB are recommended when your project requires flexible data models, horizontal scalability, or specific access patterns that do not fit the rigid schema of relational databases like PostgreSQL or MySQL. Evaluating your operational requirements guides this choice.

What's the best way to compare PostgreSQL and MongoDB for a new microservice?▼

Comparing PostgreSQL and MongoDB for a new microservice requires evaluating your data structure and access patterns. PostgreSQL provides structured relational data handling, while MongoDB offers flexible document-based storage, with the optimal choice depending on your specific operational requirements.

Does this database selection process cover specialized databases like TimescaleDB and Neo4j?▼

Yes, the database selection process covers specialized databases including TimescaleDB for time-series data, Neo4j for graph data, and vector databases like pgvector and Pinecone, ensuring you can choose the right technology for highly specific data models and access patterns.

Can I use this to evaluate my current technology stack and decide if I need a vector database?▼

Yes, you can evaluate your current technology stack to determine if migrating to a vector database like pgvector or Pinecone is necessary. The selection process analyzes your project data models and access patterns to validate your existing architecture or recommend alternatives.