In the few short years since co-authoring the Reactive Manifesto in 2013, we’ve seen the topic of Reactive go from being a virtually unacknowledged technique for constructing applications—used by only fringe projects within a select few corporations—to become part of the overall platform strategy in numerous big players in the middleware field.
One indicator of this success is that “Reactive" has become an overloaded term with people now associating it different things—in good company with words like “streaming”, “lightweight”, and “real-time.”
Our goal is to define and clarify the term “Reactive” by looking deeply at the differences between writing code in a Reactive Programming style, and the design of Reactive System architectures, where implementation techniques, tooling, and design patterns are important components of the cohesive whole.
In differentiating Reactive Programming as a distinct subset of Reactive Systems at the implementation level, this white paper aims to:
We've published the full content of this white paper in HTML, as well as a PDF download that you can save to read later. Enjoy and share! And if you'd like to speak with a Lightbend representative, simply contact us :)
