Re:Big Data Lambda Architecture
by gfodor on Wednesday January 02, 2013 @12:01PM
(#4997627)
This is a lot of platitudes but doesn't provide any specific criticisms. Most problems are "Solvable by MapReduce" since map/reduce != Hadoop but is simply an abstraction for computing functions on data in general. The architecture outlined here is a pattern for a generalized system for computing functions on data in real time that has nice properties.
[ Parent
| on HN ]
That it's an abstraction that can do anything isn't sufficient (and I'm not even convinced it's necessary): Turing machines can compute anything too, that doesn't mean they're practical.
Ok, more platitudes, still waiting for a specific criticism of this architecture and its claimed limitations.
I'll repeat myself: most big data problems fit into the mold of query = function(data), map reduce is a practical substrate for building algorithms to compute these functions, and this paper presents a practical architecture to implement these types of systems.
You made the argument that it was just platitudes and MapReduce is a sufficient model. I was specifically counter-arguing that point; that doesn't mean the claimed model is bad or that I have to reply to every single point in a single comment.