⬢ Technical Architecture
Technical Architecture is a Build-phase founder capability in the SKILLOS registry (category: new). Cross-references: 4 frameworks, 4 key metrics, 5 templates, 2 case studies, 3 mastery signals. Substrate applicability: 197 countries × 60 verticals × 99 SKILLOS sectors.
🔧 Frameworks
- Monolith-First Strategy (Martin Fowler)
- 12-Factor App Methodology
- Cloud Provider Selection Matrix
- API-First Design Principles
📊 Key Metrics
- System uptime SLA (99.9% = 8.7hr/year downtime)
- Latency p99 vs. p50 delta
- Deployment frequency (elite: multiple/day)
- Mean time to recovery (MTTR)
📋 Templates
- Architecture decision record (ADR) template
- Incident post-mortem format
- Cloud cost optimization checklist
- Security threat model canvas
- API design standards doc
💡 Case Studies
Ran as a single SQL Server monolith for years while serving 50M+ visitors/month — premature microservices would have killed velocity without adding needed scale
The Fail Whale era (2006–2009) resulted from premature architectural complexity before the team had operational maturity to manage it
The monolith vs. microservices debate is a false binary. Start with a well-structured modular monolith. Extract services when team scaling or domain isolation demands it — not before.
🎯 You've mastered this when…
- Database becomes deployment bottleneck
- Two teams blocked waiting for each other's service
- Incident root cause crosses 3+ system boundaries
Related skills in the Build phase
Frequently asked about Technical Architecture
What phase of the founder journey does Technical Architecture belong to?
It is a Build-phase skill in the SKILLOS registry. The seven phases are Foundation, Discovery, Capital, Build, Growth, Revenue, and Scale.
What are the most useful frameworks for Technical Architecture?
The four canonical frameworks are: Monolith-First Strategy (Martin Fowler); 12-Factor App Methodology; Cloud Provider Selection Matrix; API-First Design Principles.
How do I know when I have mastered Technical Architecture?
Mastery signals include: Database becomes deployment bottleneck; Two teams blocked waiting for each other's service; Incident root cause crosses 3+ system boundaries.
Which sectors does this skill apply to?
All 99 SKILLOS sectors — from AI & Machine Learning to Emerging Consumer Technology. The skill applies across every vertical in AJG's substrate of 197 countries and 60 commerce verticals.