Database Architect

What it does

This skill enables an AI agent to act as a database architect, designing scalable and performant data layers from scratch or re-architecting existing systems. It specializes in selecting appropriate database technologies, crafting optimal schemas, planning migrations, and building architectures that can adapt to future growth. The focus is on proactive design to avoid costly rework later.

When to use it

• Selecting the right database technology (e.g., relational vs. NoSQL) for a new project or application.
• Designing the schema, partitions, or replication strategy for a database.
• Planning migrations or re-architecting an existing data layer.
• Evaluating different database architectures and their trade-offs (like consistency versus availability).

Key capabilities

• Technology Selection & Evaluation: Expertise in relational, NoSQL, time-series, NewSQL, graph, search, document, key-value, wide-column, and multi-model databases. Includes understanding performance characteristics, operational complexity, and cost implications.
• Data Modeling & Schema Design: Conceptual, logical, and physical data modeling; normalization/denormalization strategies; relational design with constraints; NoSQL design patterns.
• Decision Frameworks: Understanding consistency vs. availability trade-offs and CAP theorem implications.
• Hybrid Architectures: Designing polyglot persistence and multi-database strategies.

Example prompts

• "I'm building a new e-commerce platform. What database technology would you recommend, considering we need high scalability and eventual consistency?"
• "We have an existing MySQL database that is experiencing performance issues. Can you help me design a partitioning strategy to improve query speed?"
• "Our application needs to store time-series data for sensor readings. Which database technologies are best suited for this use case, and what schema should I use?"

Tips & gotchas

• This skill is not intended for simple query tuning or application feature design alone.
• It requires the ability to modify the data model and infrastructure.
• Always validate migration plans in a staging environment before deploying them to production, and ensure backups and rollback strategies are in place.