# Design Scalable Database Architectures

Poor database choices create expensive migrations, weak performance, and operational risk. This skill turns requirements and access patterns into practical schemas, technology choices, and migration plans.

## Install

```bash
npx skillstore add sickn33/database-architect
```

## Metadata

- Status: approved
- Slug: sickn33-database-architect
- Skillstore revision: r2
- Version status: missing
- Tree hash: 573f795e9f591d7c4b49f0998eb51f2c996726beeda7b8b5a9a3f986092b8d30
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/database-architect
- Ref: f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-database-architect
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-database-architect/manifest

## Capabilities

- Compares relational, document, graph, time-series, key-value, and distributed databases against workload requirements.
- Designs conceptual, logical, and physical schemas with relationships, constraints, partitioning, and lifecycle policies.
- Recommends indexing and caching strategies from query patterns, cardinality, consistency needs, and performance targets.
- Plans versioned migrations, cutovers, validation steps, rollback procedures, backups, and zero-downtime transitions.
- Evaluates replication, sharding, multi-region resilience, security controls, compliance needs, and disaster recovery objectives.
- Produces Mermaid entity-relationship diagrams when requested.

## Use Cases

- Select a Greenfield Database: Compare storage technologies and define an initial schema from product requirements, workload patterns, team skills, and expected growth.
- Plan a Platform Migration: Create phased migration, compatibility, validation, cutover, and rollback plans for changing engines or decomposing a shared database.
- Design Regulated Data Storage: Map sensitive data, access controls, encryption, retention, audit logging, backups, and recovery requirements into a defensible architecture.

## Prompt Templates

### Choose a Database

```
Recommend a database for [application]. Expected scale is [volume], with [read/write pattern] and [consistency requirement]. Explain trade-offs and required clarifications.
```

### Design a Schema

```
Design a schema for [domain] using [database]. Include entities, relationships, constraints, indexes, retention rules, and assumptions based on these access patterns: [patterns].
```

### Plan a Safe Migration

```
Plan a migration from [source] to [target] for [data size and traffic]. Include phases, compatibility, validation, rollback triggers, backups, and cutover criteria.
```

### Architect Global Scale

```
Design a multi-region data architecture for [system]. Address consistency, partitioning, replication, failover, RPO, RTO, cost, compliance, observability, and growth to [target scale].
```

## Limitations

- Provides recommendations and examples but does not inspect a live database unless context is supplied.
- Does not execute migrations or make production changes unless separately authorized and supported by available tools.
- Requires workload details, access patterns, consistency goals, recovery objectives, and growth estimates for precise advice.
- Outputs require environment-specific validation, benchmarking, testing, and vendor documentation review.

## Best Practices

- Provide concrete read, write, latency, consistency, availability, retention, and growth requirements.
- Separate current constraints from future targets so recommendations avoid premature complexity.
- Validate architecture decisions with representative data, load tests, migration rehearsals, recovery tests, and cost estimates.

## Anti Patterns

- Choosing a database from popularity alone without documenting workload fit and operational trade-offs.
- Treating generated schemas or capacity estimates as production-ready without benchmarks and environment-specific review.
- Executing irreversible migrations without backups, staged validation, rollback criteria, and accountable approval.

## Security Audit

- Audited at: 2026-07-23T22:30:56.416\+00:00
- Summary: All ten static findings are false positives caused by ordinary database architecture language. The cited lines describe safety guidance, design patterns, constraints, and Mermaid outputs. No prompt injection, reconnaissance intent, executable behavior, or data exfiltration instructions were found in SKILL.md.

## Stats

- Views: 148
- Downloads: 13
- Favorites: 1
- Popularity score: 0