/architecture-scenario-explorer

Architecture Scenario Explorer

Explore architectural decisions through systematic scenario analysis with trade-off evaluation and future-proofing assessment.

Instructions

You are tasked with systematically exploring architectural decisions through comprehensive scenario modeling to optimize system design choices. Follow this approach: **$ARGUMENTS**

1. Prerequisites Assessment

**Critical Architecture Context Validation:**

• **System Scope**: What system or component architecture are you designing?
• **Scale Requirements**: What are the expected usage patterns and growth projections?
• **Constraints**: What technical, business, or resource constraints apply?
• **Timeline**: What is the implementation timeline and evolution roadmap?
• **Success Criteria**: How will you measure architectural success?

**If context is unclear, guide systematically:**

Missing System Scope:
"What specific system architecture needs exploration?
- New System Design: Greenfield application or service architecture
- System Migration: Moving from legacy to modern architecture
- Scaling Architecture: Expanding existing system capabilities
- Integration Architecture: Connecting multiple systems and services
- Platform Architecture: Building foundational infrastructure

Please specify the system boundaries, key components, and primary functions."

Missing Scale Requirements:
"What are the expected system scale and usage patterns?
- User Scale: Number of concurrent and total users
- Data Scale: Volume, velocity, and variety of data processed
- Transaction Scale: Requests per second, peak load patterns
- Geographic Scale: Single region, multi-region, or global distribution
- Growth Projections: Expected scaling timeline and magnitude"

2. Architecture Option Generation

**Systematically identify architectural approaches:**

Architecture Pattern Matrix

Architectural Approach Framework:

Monolithic Patterns:
- Layered Architecture: Traditional n-tier with clear separation
- Modular Monolith: Well-bounded modules within single deployment
- Plugin Architecture: Core system with extensible plugin ecosystem
- Service-Oriented Monolith: Internal service boundaries with single deployment

Distributed Patterns:
- Microservices: Independent services with business capability alignment
- Service Mesh: Microservices with infrastructure-level communication
- Event-Driven: Asynchronous communication with event sourcing
- CQRS/Event Sourcing: Command-query separation with event storage

Hybrid Patterns:
- Modular Microservices: Services grouped by business domain
- Micro-Frontend: Frontend decomposition matching backend services
- Strangler Fig: Gradual migration from monolith to distributed
- API Gateway: Centralized entry point with backend service routing

Cloud-Native Patterns:
- Serverless: Function-based with cloud provider infrastructure
- Container-Native: Kubernetes-first with cloud-native services
- Multi-Cloud: Cloud-agnostic with portable infrastructure
- Edge-First: Distributed computing with edge location optimization

Architecture Variation Specification

For each architectural option:

Structural Characteristics:
- Component Organization: [how system parts are structured and related]
- Communication Patterns: [synchronous vs asynchronous, protocols, messaging]
- Data Management: [database strategy, consistency model, storage patterns]
- Deployment Model: [packaging, distribution, scaling, and operational approach]

Quality Attributes:
- Scalability Profile: [horizontal vs vertical scaling, bottleneck analysis]
- Reliability Characteristics: [failure modes, recovery, fault tolerance]
- Performance Expectations: [latency, throughput, resource efficiency]
- Security Model: [authentication, authorization, data protection, attack surface]

Implementation Considerations:
- Technology Stack: [languages, frameworks, databases, infrastructure]
- Team Structure Fit: [Conway's Law implications, team capabilities]
- Development Process: [build, test, deploy, monitor workflows]
- Evolution Strategy: [how architecture can grow and change over time]

3. Scenario Framework Development

**Create comprehensive architectural testing scenarios:**

Usage Scenario Matrix

Multi-Dimensional Scenario Framework:

Load Scenarios:
- Normal Operation: Typical daily usage patterns and traffic
- Peak Load: Maximum expected concurrent usage and transaction volume
- Stress Testing: Beyond normal capacity to identify breaking points
- Spike Testing: Sudden traffic increases and burst handling

Growth Scenarios:
- Linear Growth: Steady user and data volume increases over time
- Exponential Growth: Rapid scaling requirements and viral adoption
- Geographic Expansion: Multi-region deployment and global scaling
- Feature Expansion: New capabilities and service additions

Failure Scenarios:
- Component Failures: Individual service or database outages
- Infrastructure Failures: Network, storage, or compute disruptions
- Cascade Failures: Failure propagation and system-wide impacts
- Disaster Recovery: Major outage recovery and business continuity

Evolution Scenarios:
- Technology Migration: Framework, language, or platform changes
- Business Model Changes: New revenue streams or service offerings
- Regulatory Changes: Compliance requirements and data protection
- Competitive Response: Market pressures and feature requirements

Scenario Impact Modeling

• Performance impact under each scenario type
• Cost implications for infrastructure and operations
• Development velocity and team productivity effects
• Risk assessment and mitigation requirements

4. Trade-off Analysis Framework

**Systematic evaluation of architectural trade-offs:**

Quality Attribute Trade-off Matrix

Architecture Quality Assessment:

Performance Trade-offs:
- Latency vs Throughput: Response time vs maximum concurrent processing
- Memory vs CPU: Resource utilization optimization strategies
- Consistency