---
title: "Project Architect - Initial Analysis"
model: "claude-sonnet"
temperature: 0.7
context: "You are a senior software architect analyzing project requirements to generate initial architecture recommendations."
---

# Initial Architecture Analysis

You are analyzing a software architecture project based on the following requirements:

## Input Data
The user has provided:
- **Project Type**: Microservices platform
- **Team Size**: 15 developers
- **Scale**: 10,000 concurrent users, 100,000 DAU
- **Data Volume**: 1 TB - 100 TB
- **Deployment**: AWS, Kubernetes (self-managed)
- **Budget**: $100K - $1M annually
- **Latency Target**: < 200ms
- **Availability**: 99.9% (43 min/year downtime)
- **Features**: Real-time updates, Multi-tenancy, Full-text search, Analytics
- **Compliance**: GDPR, SOC 2

## Your Task

Analyze these requirements and provide **3 major architecture recommendations** covering:

1. **Database Architecture**
   - Evaluate relational vs non-relational options
   - Consider read/write patterns, consistency requirements
   - Account for scale (100K DAU, 1-100TB data)
   - Recommend specific solution with rationale

2. **API Architecture**
   - Evaluate REST, GraphQL, gRPC options
   - Consider team composition and maintenance burden
   - Account for multi-tenancy and feature requirements
   - Recommend specific solution with rationale

3. **Deployment Infrastructure**
   - Evaluate deployment options on AWS
   - Consider team Kubernetes experience
   - Account for operational complexity
   - Recommend specific solution with rationale

## Output Format

For each recommendation, provide:

```
## [Component Name]

### Recommendation
**[Specific technology/pattern]**

### Why This Fits Your Requirements
- Point 1: How it addresses your constraints
- Point 2: How it handles your scale
- Point 3: How it aligns with team capacity

### Key Trade-offs
- **Pros**: [Benefits]
- **Cons**: [Costs/complexity]

### Implementation Considerations
- [Specific guidance for your project]
```

## Context for Decision Making

- Your team has Kubernetes experience ✓
- Your scale requires distributed systems thinking
- Your compliance requirements demand audit trails and encryption
- Your real-time feature requirement suggests event-based architecture
- Your budget allows for managed services (RDS, managed Kubernetes, etc.)

## Important Notes

- Be specific: name exact products/services, not categories
- Explain trade-offs clearly - no architecture is perfect
- Account for your team size (15 developers) in operational complexity
- Consider growth: How does this scale to 50K concurrent users?
- Security: GDPR compliance affects data storage and access patterns

Generate comprehensive recommendations that the team can use to make informed decisions.
