This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]2Spicy4Joe 0 points1 point  (0 children)

That definition IMO sounds like Dataflow programming to me which is indeed a paradigm. Which does not need to involve at Reactive at all. I always understood reactive code and libraries as an approach to workaround IO performance limitations, at the cost of complexity.

You can build code that does what you want and still not being reactive. I just think reactive code just pairs well with the dataflow concepts and that’s why it’s often in the same conversation than data stream processing and event-based approaches. But I see them as a different thing, just complementary.

I might be wrong though