Skip to content
BENIBIX Learn

Lambda Architecture

Data🧭 FoundationsData Pipelines

A slow, exact batch path and a fast stream path. The two are joined at the end.

Think of it like

It is like a slow, careful clerk and a fast helper. The helper gives a quick guess. The clerk fixes it at night.

Example

A shop counts page views. The speed layer shows today's rough count live. Each night the batch layer redoes the count exactly and replaces it.

Why it matters

It was an early way to get both speed and the right answer. The tools back then could do only one of those well.

Definition

Lambda architecture runs a batch path and a stream path side by side. The batch layer goes over all the data on a schedule and gets exact answers. The speed layer handles new events at once and gives quick, rough answers. A serving layer joins both, so readers see fresh and correct data. The cost is two copies of the same logic to keep in step.
Lambda keeps two paths. Kappa keeps one stream and replays it when the logic changes.

Common mistake

Forgetting the double work. Every rule must be written twice, once for each path, and the two drift apart.

Key takeaways

  1. 1
    Batch layer. Slow, exact answers over all the data.
  2. 2
    Speed layer. Fast, rough answers over new data.
  3. 3
    Serving layer. Joins both views for readers.

Compare

Learn it properly