Evaluate and Select the Right Technology Stack for Your Project
Compare and evaluate technology stack options with a scored matrix covering scalability, cost, team fit, and long-term viability.
📝 The Prompt
Act as a principal software architect with expertise across multiple technology ecosystems. Perform a comprehensive technology stack evaluation and recommendation for the following project.
Project Details:
- Project name: [PROJECT NAME]
- Project type: [Web App / Mobile App / API Platform / Data Pipeline / E-commerce / etc.]
- Brief description: [PROJECT DESCRIPTION]
- Expected users at launch: [NUMBER]
- Expected users in 2 years: [NUMBER]
- Budget for development: [BUDGET RANGE]
- Team size and expertise: [TEAM DETAILS, e.g., 3 full-stack devs experienced in Python and React]
- Key requirements: [LIST 3-5 CRITICAL REQUIREMENTS, e.g., real-time updates, HIPAA compliance, offline capability]
- Timeline to MVP: [TIMEFRAME]
Please provide:
1. **Stack Options**: Present 3 distinct technology stack options (e.g., conservative, modern, cutting-edge), each specifying:
- Frontend framework
- Backend language/framework
- Database(s)
- Hosting/Infrastructure
- Key third-party services (auth, payments, messaging, etc.)
2. **Evaluation Matrix**: Score each stack across these criteria (1-10 with justification):
- Team familiarity / learning curve
- Scalability to [EXPECTED USERS IN 2 YEARS]
- Development speed to MVP
- Long-term maintainability
- Community support and ecosystem maturity
- Total cost of ownership (2-year estimate)
- Hiring pool availability
- Security and compliance fit
3. **Recommendation**: Provide a clear winner with rationale
4. **Risk Mitigation**: Top 3 technical risks with the recommended stack and how to address them
5. **Migration Path**: How to evolve the stack if requirements change dramatically
💡 Tips for Better Results
Weight team familiarity heavily for early-stage projects — the best stack is the one your team can ship with fastest. Always estimate the 2-year total cost of ownership including hosting, licensing, and DevOps overhead, not just development cost. Avoid choosing bleeding-edge tech for mission-critical systems unless you have deep expertise.
🎯 Use Cases
CTOs, technical co-founders, and engineering leads selecting or re-evaluating the technology stack for a new product build or major platform migration.