when I first heard about the idea of building an system around a log of events, they called it event sourcing. in 2014, it got reinvented as "kappa architecture"
I dislike this term because it sounds fancy but "kappa" doesn't even make sense in hindsight, but "event sourcing" does make sense - the source of everything in the system is events.
The idea of Kappa Architecture was first described in an article by Jay Kreps from LinkedIn. Then came the talk “Turning the database inside out with Apache Samza” by Martin Kleppmann at 2014 StrangeLoop which inspired this web site.
hmm, when people talk about Event Sourcing, they normally are talking about designing an application that can regenerate the state from events - all state is captured as events. When people talk about kappa architecture it's a Big Data thing... hmm
EventDrivenArchitecture (EDA) is a distributed information systems architectural style complementary to ServiceOrientedArchitecture (SOA). It was arguably coined by the GartnerGroup's RoySchulte in the late 1990's.
hmm, it's starting to seem like Event Driven Architecture did catch on very strongly, then later had a comeback as Kappa Architecture... it's a generational thing. prehaps the best thing is to use the term that has had more impact recently (looks like kappa) but acknowledge that the idea actually comes from the late 90s (as event driven architecture)
when I first heard about the idea of building an system around a log of events, they called it event sourcing. in 2014, it got reinvented as "kappa architecture"
I dislike this term because it sounds fancy but "kappa" doesn't even make sense in hindsight, but "event sourcing" does make sense - the source of everything in the system is events.
https://milinda.pathirage.org/kappa-architecture.com/ (top result for "kappa architecture")
that article https://www.oreilly.com/ideas/questioning-the-lambda-architecture is dated july 2014.
however, "Event Sourcing" is described in 2005
hmm, when people talk about Event Sourcing, they normally are talking about designing an application that can regenerate the state from events - all state is captured as events. When people talk about kappa architecture it's a Big Data thing... hmm
Wikipedia doesn't even have an article on "kappa architeture" but it has an article on https://en.wikipedia.org/wiki/Lambda_architecture (the same thing, but you also have batch processes) There is also an article on "event driven architecture" https://en.wikipedia.org/wiki/Event-driven_architecture which references the event sourcing article.
wiki.c2.com (this was first ever wiki, lots of great stuff on here) has an article http://wiki.c2.com/?EventDrivenArchitecture
hmm, it's starting to seem like Event Driven Architecture did catch on very strongly, then later had a comeback as Kappa Architecture... it's a generational thing. prehaps the best thing is to use the term that has had more impact recently (looks like kappa) but acknowledge that the idea actually comes from the late 90s (as event driven architecture)