What Three Fictional Startups Taught Me About Structured, Semi-Structured, and Unstructured Data on Azure

Short summary

Learning cloud databases through fictional case studies reveals a critical insight: data type classification (structured/semi-structured/unstructured) is distinct from database selection. Azure requires different stores based not just on data shape, but on volume, velocity, and access patterns—structured GPS data at high ingestion rates belongs in Cosmos DB, not SQL. Rendered outputs like PDFs are unstructured despite internal structure, and semi-structured metadata can live separately from raw content.

• •Data type ≠ database choice; volume and velocity matter equally in Azure storage decisions
• •Structured data at high velocity (like GPS tracking every 30s) requires NoSQL engines for performance
• •Rendered formats (PDFs) count as unstructured even if underlying data is structured; metadata can split across tiers

Generated with AI, which can make mistakes.