Technology Selection Matrix
Published on
Archive note: This study note is retained for historical reference and is not part of the curated Learn path.
A technology matrix can organize discovery, but product names should not substitute for requirements. Compare candidates using the workload’s latency, throughput, consistency, durability, security, recovery, operability, skills, support, cost, and exit requirements.
Evaluate the complete lifecycle: provisioning, upgrades, observability, backup, restoration, incident response, capacity, deprecation, and migration. Validate uncertain behavior with a bounded prototype and record the decision, rejected alternatives, consequences, and revisit trigger.
Use the curated Systems Architecture path for the current decision framework.