Backend Architecture Decision Framework
Evaluate backend tradeoffs and make informed architecture decisions
What You Can Do
This skill helps you systematically evaluate architectural options for your backend systems by analyzing tradeoffs across scalability, performance, maintainability, and cost. You'll receive a structured decision framework that compares candidate technologies and patterns against your specific constraints—team size, timeline, budget, and operational complexity. Get clear recommendations backed by real-world considerations, not just theory.
Features
Systematically compare scalability vs. complexity, consistency vs. availability, and cost vs. performance across different architecture options
Evaluate databases, caching layers, message queues, and other components on criteria relevant to your use case
Factor in your team's size, existing infrastructure, operational expertise, budget, and timeline to make realistic suggestions
Identify operational, technical, and organizational risks for each architecture option with mitigation strategies
Get phased implementation paths for transitioning from your current architecture to a recommended design
Work through interactive decision trees for when to shard databases, introduce caching, separate services, or add read replicas
Compare infrastructure costs, engineering velocity impact, and operational overhead for each option
Example Output
Architecture Decision: User Service Scaling
Recommended Approach: Service-Oriented Architecture with read replicas
Tradeoff Summary:
- ✅ Scales to 100K+ concurrent users
- ✅ Read latency: <50ms (vs. 500ms+ with monolith)
- ✅ Team can work independently
- ⚠️ Requires distributed transaction handling
- ⚠️ Operational complexity increases 3-4x
Technology Scorecard:
| Component | PostgreSQL+Read Replicas | DynamoDB | Cassandra |
|---|---|---|---|
| Scalability | 8/10 | 10/10 | 9/10 |
| Operational Simplicity | 9/10 | 8/10 | 4/10 |
| Query Flexibility | 10/10 | 6/10 | 5/10 |
| Cost (at 1M req/day) | $800/mo | $1200/mo | $2000/mo |
| Your Match Score | 9/10 | 7/10 | 5/10 |
Phased Implementation:
- Add read replicas to existing PostgreSQL (2 weeks)
- Introduce application-level caching layer (Redis, 3 weeks)
- Extract auth service into separate deployment (4 weeks)
- Monitor and optimize query patterns
What's Included
- Decision Framework Template: Structured prompts to guide you through evaluating any architectural choice systematically
- Technology Comparison Matrices: Pre-built evaluation criteria for databases, caches, message queues, search engines, and deployment platforms
- Scaling Decision Trees: Interactive flowcharts for common scaling decisions: monolith vs. microservices, SQL vs. NoSQL, caching strategies
- Cost-Benefit Calculator: Framework for estimating infrastructure costs, engineering time, and operational overhead for each option
- Risk Assessment Checklists: Identify technical risks, operational risks, and team capacity constraints for each architecture
Who It's For
- Backend Architects
- Technical Leads evaluating system redesigns
- Engineering Managers planning scaling work
- CTO/VP Engineering making technology bets
- Startup founders making early technology choices
Best For
- Technology selection during architecture reviews
- Scaling decisions when traffic or data volume increases
- Evaluating monolith vs. microservices migration
- Database or caching layer selection
- Planning infrastructure migrations







