Medieros, Andre. "Dynamics of Change: Why Reactivity Matters." GALILEO. N.p., Oct. 2016. Web. 4 Nov. 2016.
The article defines two types of programming. “Passive” programming is writing code where one object affects another, but the object being acted on doesn’t contain much of the code that’s doing work. In passive programming the object that triggers the change in the second object has all the code that makes the change. “Reactive” programming is where the code to change an object is located in the object itself. The object that triggers the change can call a function inside the targeted object, but it doesn’t actually contain the function that’s making the change. The article argues that “Reactive” programming is an important thing to think about because it separates different jobs in the code between objects that “own” those jobs. “Introducing reactive patterns in an architecture can help better define which module owns a relationship of change between two modules. “ (Medieros 5)
The article defines two types of programming. “Passive” programming is writing code where one object affects another, but the object being acted on doesn’t contain much of the code that’s doing work. In passive programming the object that triggers the change in the second object has all the code that makes the change. “Reactive” programming is where the code to change an object is located in the object itself. The object that triggers the change can call a function inside the targeted object, but it doesn’t actually contain the function that’s making the change. The article argues that “Reactive” programming is an important thing to think about because it separates different jobs in the code between objects that “own” those jobs. “Introducing reactive patterns in an architecture can help better define which module owns a relationship of change between two modules. “ (Medieros 5)