Database Technology Selection

Explore database options for this use case.

Requirements:
{{requirements}}

Data characteristics: {{data_characteristics}}
Scale expectations: {{scale}}

## OPTION 1: Relational Database (PostgreSQL/MySQL)
- How well does it fit the requirements?
- Strengths for this use case: [list]
- Weaknesses for this use case: [list]
- Operational complexity: [low/medium/high]
- Team expertise: [low/medium/high]
- Score: [1-10]

## OPTION 2: Document Database (MongoDB)
- How well does it fit the requirements?
- Strengths for this use case: [list]
- Weaknesses for this use case: [list]
- Operational complexity: [low/medium/high]
- Team expertise: [low/medium/high]
- Score: [1-10]

## OPTION 3: Key-Value Store (Redis/DynamoDB)
- How well does it fit the requirements?
- Strengths for this use case: [list]
- Weaknesses for this use case: [list]
- Operational complexity: [low/medium/high]
- Team expertise: [low/medium/high]
- Score: [1-10]

## OPTION 4: Hybrid Approach
- What combination might work best?
- Architecture overview
- Trade-offs
- Score: [1-10]

## RECOMMENDATION
- Selected option with rationale
- Migration path if applicable