Skip to content
BENIBIX Learn

Lambda Architecture vs Kappa Architecture

People think Kappa is just Lambda with a part cut off, and it is more than that. Lambda runs the same logic twice, once in a nightly batch and once live, and joins the two. Kappa runs it once, in a stream. When the logic changes, Kappa replays its log from the start instead of keeping a batch path.

Data🧭 Foundations

Lambda Architecture

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

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.

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.
Full entry
Data🧭 Foundations

Kappa Architecture

One stream does all the work. Old data is played again when rules change.

Kappa architecture uses only a stream, with no separate batch path. Every event is kept in a log that can be read again. Live data flows through one stream job. When the logic changes, you replay the old events through the new job. So there is one set of code to write and fix.

Example
A team changes how it counts active users. It starts the new job at the oldest event in the log and lets it catch up.
Why it matters
It removes the double code of Lambda. One job means one place for bugs and one place to fix them.
Full entry

In one line

Lambda Architecture
A slow, exact batch path and a fast stream path. The two are joined at the end.
Kappa Architecture
One stream does all the work. Old data is played again when rules change.