database-designer-skill

SQL vs NoSQL decisions are evaluated based on access patterns, scalability needs, and non-functional requirements. The Skill aligns the database type selection with your architecture artifacts to present up to three options with pros and cons.

Database schema design is defined by mapping architecture and backend artifacts to schema models, collections, and indexes. The Skill asks clarifying questions when requirements are incomplete to ensure the proposed data storage strategy fits your workloads.

Data lifecycle policies are established by defining data storage strategies aligned with your architecture artifacts. The Skill provides recommendations for typical backend workloads, including migrations and lifecycle management.

You can get database platform recommendations with explicit trade-offs and alternatives. The Skill evaluates your backend requirements and presents up to three architecture-aligned options for user selection.

Database schema design requires clarifying questions when requirements are incomplete to accurately define the data storage strategy. This ensures the proposed schema models, indexes, and platform choices match your specific backend workloads.

A NoSQL database might not suit your data storage strategy if your access patterns require strict relational consistency or complex transactions. The Skill evaluates these constraints against your non-functional requirements to recommend the appropriate platform.