Loading content
Lambda Architecture is a structural architectural principle for large-scale data processing that separates batch and speed pipelines. It defines batch, speed and serving layers to combine accuracy with low latency. Typical decisions involve trade-offs around consistency, complexity and operational cost in data integration.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
Lambda architecture is a data-processing pattern that processes the same data through a batch path and a fast real-time path, then combines both results in a serving layer.
Nathan Marz coined Lambda architecture in the context of large-scale data and distributed computing. It addressed the tension between complete but slow batch computation and fast, potentially incomplete real-time processing; streaming frameworks now offer alternative implementations.
Think of two roads leading to one destination: the batch layer computes a complete baseline, the speed layer adds recent events, and the serving layer answers queries from both results.
It processes the complete dataset and corrects earlier approximations.
It processes new events with low delay until batch computation catches up.
The pattern shows how systems can combine completeness and freshness. It is useful when queries must respond immediately while a full recomputation remains feasible on a regular basis.
Where this building block is located in the topic model.
No structure path available.
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.