This is a click-through primer, not a slideshow. Every card, stage, and layer below responds to a click — explore them in any order to build the full picture.
Before "big data" meant a tech stack, it meant a problem definition. Click each letter to see why traditional databases struggle with it.
The sheer scale of data generated — often too large to fit on a single machine's disk or process in memory at once.
The speed at which new data arrives and must be acted on — sometimes in real time, not in nightly batches.
The mix of structured, semi-structured, and unstructured formats — tables, JSON logs, images, free text, audio.
Raw data becomes a decision through four stages. Click a stage to see what actually happens there and which tools are typically used.
Pull data from its source
Land it somewhere durable
Clean, join, transform
Query, model, visualize
Data enters the system from APIs, application logs, IoT sensors, or third-party feeds — often continuously, not as a one-time export.
Most real systems are layered — each layer trades off durability, speed, and cost differently. Click a layer to expand it.
Brings data in from outside the system, often as continuous streams. Tools like Kafka or Kinesis buffer incoming events so downstream systems aren't overwhelmed by spikes.
Holds raw and processed data cheaply at scale — distributed file systems (HDFS), object storage (S3), or data lakes that don't require a fixed schema up front.
Transforms raw data into something usable — distributed engines like Spark or Flink run computations across many machines in parallel.
Exposes results to people and applications — dashboards, BI tools, or APIs that let analysts and downstream systems query the processed data.
One question to confirm the idea stuck.