NEW
Original big data heuristic: volume, velocity, and variety highlight scale, speed, and diversity challenges.
DESCRIPTION
The 3Vs framework, popularized by Doug Laney, characterizes big data by volume, velocity, and variety. It guided early architectural choices for handling large, fast, diverse data sources. Over time, extensions introduced veracity and value, forming the 5Vs. The 3Vs remain useful for framing core technical challenges. They continue to inform storage, processing, and integration strategies.
ALTERNATIVE DEFINITIONS
Oracle
Big data is often characterized by the three V’s: volume, velocity, and variety.
Introduces the original three attributes as defining characteristics.
SAS
The three Vs of big data—volume, velocity, and variety—describe the dimensions that make data big.
Emphasizes the dimensional aspects that drive big data challenges.
IBM
Big data is commonly described using the three V’s: volume, velocity, and variety.
States the widely used three-attribute framing from major vendor perspective.
RELATED TERMS
Big Data Data Volume Data Velocity Data Variety Scalability Stream Processing Data Lake Data Warehouse Data Quality
COMPETING TERMS
RELATIONS
- Broader: Big Data
KNOWLEDGE AREAS
Data Management Data Architecture Data Science
TARGET AUDIENCE
Chief Data Officer Data Strategy Consultant Data Architect Data Scientist
EXTERNAL SOURCES
- Wikipedia - Big data
- Oracle - Oracle big data overview including 3Vs
- SAS - Vendor overview explaining Vs
- IBM - IBM framing of big data attributes
TOP QUESTIONS
Why did the 3Vs become popular in big data?
They succinctly captured core challenges of scale, speed, and diversity that drove new architectures.
Category: Origin
How does each V affect system design?
Volume impacts storage and partitioning; velocity drives streaming choices; variety requires flexible schemas and integration.
Category: Requirements
Are the 3Vs sufficient today?
They remain useful but are often complemented by veracity and value in the 5Vs.
Category: Opinion
What is a common misuse of the 3Vs?
Treating them as a checklist rather than a lens to guide context-specific trade-offs.
Category: Mistakes
How do 3Vs inform data governance?
Variety and volume increase need for metadata, lineage, and quality controls; velocity demands timely validation.
Category: Management
What technologies address the 3Vs?
Distributed storage, stream processing, schema-on-read lakes, and flexible integration patterns.
Category: Application
How should organizations apply the 3Vs?
Assess data characteristics, map to capability gaps, and prioritize investments to handle each V.
Category: HowTo
When did the 3Vs originate?
They were popularized around 2001 in industry analysis on data growth and complexity.
Category: Origin
How do 3Vs relate to scalability?
Volume and velocity require elastic scaling; variety needs adaptable models and pipelines.
Category: Definition