approach-evaluation

To compare architectural approaches objectively, you research industry standards and evaluate viable solutions against project-specific constraints like stack compatibility and operational fit. This structured comparison surfaces trade-offs such as potential lock-in and maintenance costs without making a final decision for you.

Evaluating microservices versus a monolithic approach requires researching both architectural patterns and comparing them against defined criteria such as scalability, maintainability, and team expertise. The analysis presents factual trade-offs and gains for a human decision-maker to review.

Technical comparison works by researching current trends and best practices to discover practical solutions, then structuring a factual comparison against defined criteria. It clearly outlines the gains, costs, and potential vendor lock-in associated with each identified architectural option.

You can use approach evaluation for any technical or architectural problem statement, provided you supply sufficient context. It requires memory and artefact inputs to resolve project specifics and compare viable approaches against your defined constraints.

You should not use automated technical comparison when a final architectural decision is required, as it explicitly avoids making the choice for you. It is designed to surface trade-offs and factual constraints, leaving the ultimate decision to a human reviewer.