Reactive Programming. A Brief Analysis in the Context of Programming Paradigms

This work aims to clarify the reader about what reactive programming represents, its importance, necessity, and applicability, primarily following the historical evolution of this concept, as well as the way in which the established people of the computer field debate and define this term. Reactive programming allows for a non-lockable execution, in which the execution threads that compete for a shared resource do not have to wait; in this way, they can perform other useful things while the resource is occupied. On the other hand, synchronous calls are characterized by blocking the thread until a response is obtained that can be returned. Everything that is current in the technological world and in everyday life has a significant dose of programming behind it. Over time, the demands of the market and users have made that, in addition to this intelligent component of programming, a reactive, interactive part is also necessary. This is where the concept of reactive programming comes in. But what exactly is reactive programming? And why is this necessary? Why is it necessary and what is the difference from other languages? Here are some of the questions we will try to answer in this work.