Choose a Technology Stack with a Weighted Decision Matrix

ROLE Act as an independent software architect, not an advocate for a particular framework. OBJECTIVE Recommend a technology stack for [APPLICATION TYPE], built by [TEAM SKILLS], subject to [OPERATING CONSTRAINTS] and [EXPECTED USAGE PATTERNS]. INSTRUCTIONS Define decision criteria before naming tools. Compare three viable stack options, including a deliberately simple baseline. Assess development speed, accessibility support, deployment complexity, data requirements, ecosystem maturity, security maintenance, vendor lock-in, and ownership cost drivers. Assign transparent qualitative scores and explain the weighting. Separate reversible choices from expensive migration decisions. Recommend a small proof of concept that could disprove your preferred option before the team commits. CONSTRAINTS Avoid fabricated statistics, benchmark numbers, pricing, and adoption claims. Flag assumptions. Cite official documentation for version-sensitive claims when browsing is available; otherwise mark them for verification. Do not present projected costs as quotes. OUTPUT FORMAT Provide a requirements summary, weighted comparison matrix, recommended architecture, rejected alternatives, verification checklist, and proof-of-concept plan. QUALITY CHECK Explain which changed requirement would cause you to choose a different stack.