Talk:Lambda architecture

History

I'm surprised that this article makes no reference to the history of the term. Its minting is of recent vintage:

Nathan Marz came up with the term Lambda Architecture (LA) for a generic, scalable and fault-tolerant data processing architecture, based on his experience working on distributed data processing systems at Backtype and Twitter. http://lambda-architecture.net/

... it also seems odd that there's no mention of how Clojure's approach to mutability and state (its preference for functional programming, and thus the link to "lambda functions" and the "Lambda Calculus") influenced Marz in coining this terminology.

This would be a good section to add and one that I've had in mind to add. I think what's written above is generally correct history as far as I know. Of course, it will require good references. textractor (talk) 04:09, 23 October 2014 (UTC)

Comparison with other methods

Would be interesting to see this compared with other methods, e.g. Kappa Architecture. (http://radar.oreilly.com/2014/07/questioning-the-lambda-architecture.html) As Kreps notes, "Fundamentally, though, there is nothing that ties this idea to Kafka. You could substitute any system that supports long retention of ordered data (for example HDFS, or some kind of database). Indeed, a lot of people are familiar with similar patterns that go by the name Event Sourcing or CQRS. And, of course, the distributed database people will tell you this is just a slight rebranding of materialized view maintenance, which, as they will gladly remind you, they figured out a long long time ago, sonny." --162.95.216.222 (talk) 20:20, 19 August 2015 (UTC)

In the section See Also, is AWS Lambda irrelevant?

They have the same name but AWS Lambda is not related to the topic of this article. Should that be removed or perhaps moved to a disambiguation section before the article? I vote removed Razziabuissa (talk) 05:49, 23 December 2023 (UTC)