I would say its kind of its own architecture.
Let’s say the common components are Couchbase, Kafka, Spark / Storm, and Hadoop. They can be arranged in any order, and the data can flow in any direction. Lambda architecture is just one arrangement and flow, and it is a solution to a very specific problem. We see lots of arrangements and flows.
- Kafka to Storm/Spark to Couchbase to Hadoop
- Couchbase to Kafka to Hadoop
- Log to Hadoop to Couchbase
- Couchbase to Hadoop to Couchbase
The first one is what the big data site focuses on. However, you can create your own architecture by reordered components or add/removing them. That’s the fun part.
More on Lambda here: http://blog.couchbase.com/lamda-architecture-and-beyond-with-nosql