4 ms·
> But I found it a little bit weird that they used the term "reactive" in the title "Reactive" is the new cool term that replaced "async" and "non-blocking" fr
by rdtsc 11y ago
> But I found it a little bit weird that they used the term "reactive" in the title
"Reactive" is the new cool term that replaced "async" and "non-blocking" from a few years ago.
For maximum impact it is advised to combine it with microservices (or even unikernels) in the same sentence.
- fredliu 11y agoah, thanks for the explanation... I guess we probably need a "new_cool_term" namespace for every new/re-purposed term. Simply use "reactive" to refer to "async" already caused a name collision for me here....
- oldmanjay 11y agoIt's not a direct replacement for asynchronous, as reactive implies quite a different set of semantics. The collision is only in your misunderstanding of the pattern. The jargon is meaningful, not marketing.
- xirdstl 11y agoAnd to completely blow everyone's mind, add 'dockerized'.
- nostrademons 11y agoFWIW, "async" was called the "Reactor Pattern" in the Design Patterns world back in 2000: https://en.wikipedia.org/wiki/Reactor_pattern https://en.wikipedia.org/wiki/Reactor_pattern
- ttflee 11y agoBut "(a)ll reactor systems are single threaded by definition"...
- nostrademons 11y agoSo is what we know of as "async" and "non-blocking". The point is that instead of spinning up many blocking threads, a single select/poll/epoll() call triggers a set of callbacks.
- rdsubhas 11y agoI refuse to believe its a "Pattern" until I find a AsyncReactiveReactorFactoryFactory class.
- cfontes 11y agoAlso add containers to the mix and have a promotion tomorrow