Building a lamda architecture

So, in recently researching lamda architectures I came across these links, and I thought some were worth sharing here:

This document has a great slide, which shows how you keep the data stores separate, but merge at the serving layer:

https://www.mapr.com/developercentral/lambda-architecture

 

 

 

Just to keep things interesting, there is a subtly different view here: (Linkedin guy)

 

https://www.oreilly.com/ideas/questioning-the-lambda-architecture

 

That solution is not dissimilar to this document here:

 

http://blog.cloudera.com/blog/2015/11/how-to-ingest-and-query-fast-data-with-impala-without-kudu/

 

An important comment about the fundamental principle of immutable data in lamdba:

 

https://www.talend.com/blog/2016/05/31/the-lambda-architecture-and-big-data-quality

 

(Don’t worry, the page is nothing about Talend itself – A common marketing trick that tech companies seem to be using a lot these days – talk about cool tech, just to get yourself linked to. Oh damnit, I just did that. Damn!)

Then there’s the outsider – Kudu.  Kudu seems to be going back to mutability.  BUT kudu is far from being suitable for production use, and it has a horrible deployment architecture.

 

 

Finally, inquidia (BigData Pentaho partners in the states) have a page on it, a good summary of the options, latency implications etc. This can be found here:

 

http://inquidia.com/news-and-info/hadoop-how-update-without-update