Loading content
BigQuery allows for the storage and real-time analysis of large datasets. It provides a powerful SQL query interface and seamless integrations with other Google Cloud services. Companies leverage BigQuery for complex data analyses and to support data-driven decision-making.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
BigQuery is a serverless distributed data warehouse from Google Cloud for analytical SQL over very large datasets.
Google developed BigQuery from internal technologies such as Dremel and released it in 2010 for column-oriented massively parallel analytics.
Data lives in tables with columnar storage. A query plan distributes work across many slots, reads only needed columns, and aggregates results hierarchically. Partitioning and clustering reduce scans, while storage and compute are largely managed separately.
SQL is split into parallel stages across many compute units.
Partitions and clusters limit data read.
Scanned bytes or reserved capacity determine performance and cost.
BigQuery fits large analytics, logs, and data-lake queries without cluster operation. Data model, query hygiene, permissions, and cost controls remain necessary; frequent transactions belong elsewhere.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.