Re:Questioning the Lambda Architecture (2014)
by cube2222 on Tuesday February 25, 2020 @02:05AM
(#22411413)
If you’re interested in stuff like this, check out “streaming 101: the world beyond batch”[1], it’s a great blog post series about exactly once event time streaming.
And keep an eye on OctoSQL[2] too, as we’ll soon be making a big release making everything streaming friendly (with pure sql obviously!).
We’ve been really inspired with articles like this one.
Re:Questioning the Lambda Architecture (2014)
by mtreis86 on Monday February 24, 2020 @08:59PM
(#22410342)
Why are developers continually attributing new meaning to old terms? This has nothing to do with Lambda Calculus, anonymous functions, or Lisp. Why call it Lambda Architecture?
Re:Questioning the Lambda Architecture (2014)
by nine_k on Monday February 24, 2020 @11:05PM
(#22410826)
Because people tend to want a nicely-sounding, familiar-looking name. So they reuse the same set of familiar words. They get overburdened with meanings, but also even more familiar-sounding.
It takes some guts and talent to name something with an alien, original word, like Google, or Atari, or Motorola.
Re:Questioning the Lambda Architecture (2014)
by voodoomagicman on Tuesday February 25, 2020 @01:39AM
(#22411350)
I was curious too - "Paul Galvin wanted a brand name for Galvin Manufacturing Corporation's new car radio, and created the name “Motorola” by linking "motor" (for motorcar) with "ola" (from Victrola), which was also a popular ending for many companies at the time, e.g. Moviola, Crayola."
Re:Questioning the Lambda Architecture (2014)
by nine_k on Tuesday February 25, 2020 @07:46AM
(#22412697)
Neither "googol" nor "atari" (a very clever Japanese import) were common English words. Stuff like "lambda", or "spark", or "react" are more or less everyday words, with well-established previous everyday meanings.
Re:Questioning the Lambda Architecture (2014)
by mjfisher on Tuesday February 25, 2020 @01:50AM
(#22411380)
I believe the Lambda Architecture is a simplified refinement of a previous idea, the Kappa Architecture. It's just one letter further along. I have no idea why a Kappa Architecture was named as such.
And keep an eye on OctoSQL[2] too, as we’ll soon be making a big release making everything streaming friendly (with pure sql obviously!).
We’ve been really inspired with articles like this one.
[1]: https://www.oreilly.com/radar/the-world-beyond-batch-streami...
[2]: https://github.com/cube2222/octosql
It takes some guts and talent to name something with an alien, original word, like Google, or Atari, or Motorola.
We're you thinking of event sourcing?
https://martinfowler.com/eaaDev/EventSourcing.html
This seems more like a janky solution for being able to reprocess streams after the code has changed in order to recompute results.