dataplatform-advisor

Choosing the right data platform architecture requires classifying your workload across latency, freshness, concurrency, query shape, and consistency to map it to an optimal storage archetype. This framework enforces a structured decision process to reduce guesswork and ensure repeatable outcomes.

The best way to classify data workloads for system selection is evaluating them across latency, freshness, concurrency, query shape, consistency, and data quality. This structured classification maps directly to primary storage systems and recommended alternatives.

You document trade-offs during a data architecture migration by applying a formal decision framework that requires clearly defined constraints, inputs, and outputs. This process ensures repeatable, auditable outcomes using provided trade-off analysis templates.

Yes, you can use this decision framework for both data migrations and performance optimization. It identifies optimal data system choices by mapping workload archetypes and analyzing trade-offs where latency, freshness, and concurrency drive system selection.

You should not use a formal archetype mapping process when your workload constraints, inputs, and outputs are not clearly defined. The framework requires these strict parameters to enforce a structured decision process and ensure repeatable, auditable outcomes.