Reactive Programming - Revision history

Miranda ricardo: /* Asynchronous dataflow */

2014-10-14T21:54:39Z

‎Asynchronous dataflow

Miranda ricardo: /* Synchronous dataflow */

2014-10-14T21:54:17Z

‎Synchronous dataflow

Miranda ricardo: /* Decoupling data from operations on data */

2014-10-14T16:45:21Z

‎Decoupling data from operations on data

Miranda ricardo: /* Decoupling data from operations on data */

2014-10-14T16:31:02Z

‎Decoupling data from operations on data

Miranda ricardo: /* Decoupling data from operations on data */

2014-10-14T16:23:42Z

‎Decoupling data from operations on data

Miranda ricardo: /* Decoupling data from operations on data */

2014-10-14T11:46:22Z

‎Decoupling data from operations on data

Miranda ricardo: /* Decoupling data from operations on data */

2014-10-14T11:44:20Z

‎Decoupling data from operations on data

Miranda ricardo at 11:36, 14 October 2014

2014-10-14T11:36:42Z

Miranda ricardo at 11:29, 14 October 2014

2014-10-14T11:29:21Z

Miranda ricardo: Created page with "According to Wikipedia[http://en.wikipedia.org/wiki/Reactive_programming] "(...) reactive programming is a programming paradigm oriented around data flows and the propagation of ..."

2014-10-14T11:28:12Z

Created page with "According to Wikipedia[http://en.wikipedia.org/wiki/Reactive_programming] "(...) reactive programming is a programming paradigm oriented around data flows and the propagation of ..."

New page

According to Wikipedia[http://en.wikipedia.org/wiki/Reactive_programming] "(...) reactive programming is a programming paradigm oriented around data flows and the propagation of change. This means that it should be possible to express static or dynamic data flows with ease in the programming languages used, and that the underlying execution model will automatically propagate changes through the data flow."

"For example, in an '''imperative programming setting''', <math>a := b + c</math> would mean that <math>a</math> is being assigned the result of <math>b + c</math> in the instant the expression is evaluated. Later, the values of <math>b</math> and <math>c</math> can be changed with no effect on the value of <math>a</math>."

"In '''reactive programming''', the value of <math>a</math> would be automatically updated based on the new values."

== MS Excel is a reactive programming environement ==
Continuing from Wikipedia[http://en.wikipedia.org/wiki/Reactive_programming] "A modern spreadsheet program is an example of reactive programming. Spreadsheet cells can contain literal values, or formulas such as "=<math>B1+C1</math>" that are evaluated based on other cells. Whenever the value of the other cells change, the value of the formula is automatically updated."

@@ Line 15: / Line 15: @@
 === Asynchronous dataflow ===
-According to Matt Carcki[https://leanpub.com/dataflowbook] "Asynchronous execution is when a node fires any time that its activation preconditions are met, possibly at the same time as other nodes."
+According to Matt Carcki[https://leanpub.com/dataflowbook] "Asynchronous execution is when a node fires any time that its activation preconditions are met, possibly at the same time as other nodes".
 === Synchronous dataflow ===
 Still according to Matt Carcki[https://leanpub.com/dataflowbook] "Synchronous execution is when the nodes fires on a pre-calculated, fixed schedule. This implies that the program has to be compiled first to build the schedule. The schedule determines which nodes have to fire before others, how often they have to fire and which nodes can fire simultaneously". Synchronous dataflow requires the token rate to be known at design time.

← Older revision		Revision as of 21:54, 14 October 2014
Line 18:		Line 18:

	=== Synchronous dataflow ===		=== Synchronous dataflow ===
−	Still according to Matt Carcki[https://leanpub.com/dataflowbook] "Synchronous execution is when the nodes fires on a pre-calculated, fixed schedule. This implies that the program has to be compiled first to build the schedule. The schedule determines which nodes have to fire before others, how often they have to fire and which nodes can fire simultaneously."	+	Still according to Matt Carcki[https://leanpub.com/dataflowbook] "Synchronous execution is when the nodes fires on a pre-calculated, fixed schedule. This implies that the program has to be compiled first to build the schedule. The schedule determines which nodes have to fire before others, how often they have to fire and which nodes can fire simultaneously". Synchronous dataflow requires the token rate to be known at design time.
−
−	Synchronous dataflow requires the token rate to be known at design time.

@@ Line 19: / Line 19: @@
 === Synchronous dataflow ===
 Still according to Matt Carcki[https://leanpub.com/dataflowbook] "Synchronous execution is when the nodes fires on a pre-calculated, fixed schedule. This implies that the program has to be compiled first to build the schedule. The schedule determines which nodes have to fire before others, how often they have to fire and which nodes can fire simultaneously."
 Synchronous dataflow requires the token rate to be known at design time.

@@ Line 10: / Line 10: @@
 == Decoupling data from operations on data ==
 To have a data flow between nodes it is necessary to decouple data from operations on data. Messages, tokens in data flow parlance, are send from node to node through arcs.
-Dut to the non-deterministic nature of a large system like Mohid, a asynchronous approach was choosen, using the Hollywood principle (stated as "don't call us, we'll call you."[http://en.wikipedia.org/wiki/Hollywood_principle]). Here we will focus on asynchronous reactive dataflow systems, focusing on the actor model. Reactive daflow systems can be:
+Dut to the non-deterministic nature of a large system like Mohid, a asynchronous approach was chosen, using the Hollywood principle (stated as "don't call us, we'll call you."[http://en.wikipedia.org/wiki/Hollywood_principle]). Here we will focus on asynchronous reactive dataflow systems, focusing on the actor model. Reactive dataflow systems can be:
 *asynchronous; or
 *synchronous.
 === Asynchronous dataflow ===
 === Synchronous dataflow ===

← Older revision		Revision as of 16:23, 14 October 2014
Line 9:		Line 9:

	== Decoupling data from operations on data ==		== Decoupling data from operations on data ==
−	To have a data flow between nodes it is necessary to decouple data from operations on data. Messages, tokens in data flow parlance, are send from node to node. ~~To have a more robust design inherently~~ non-deterministic, ~~the system should be~~ asynchronous, using the Hollywood principle (stated as "don't call us, we'll call you."[http://en.wikipedia.org/wiki/Hollywood_principle]).	+	To have a data flow between nodes it is necessary to decouple data from operations on data. Messages, tokens in data flow parlance, are send from node to node through arcs.
		+	Dut to the non-deterministic nature of a large system like Mohid, a asynchronous approach was choosen, using the Hollywood principle (stated as "don't call us, we'll call you."[http://en.wikipedia.org/wiki/Hollywood_principle]). Here we will focus on asynchronous reactive dataflow systems, focusing on the actor model. Reactive daflow systems can be:
		+	*asynchronous; or
		+	*synchronous.
		+
		+	=== Asynchronous dataflow ===
		+
		+	=== Synchronous dataflow ===

← Older revision		Revision as of 11:46, 14 October 2014
Line 9:		Line 9:

	== Decoupling data from operations on data ==		== Decoupling data from operations on data ==
−	To have a data flow between nodes it is necessary to decouple data from operations on data. Messages, tokens in ~~dataflow~~ parlance, are send from node to node. To have a more ~~roubust~~ design ~~inherentely~~ non-deterministic, the system should be ~~assynchronous~~, using the Hollywood principle is stated as "don't call us, we'll call you."[http://en.wikipedia.org/wiki/Hollywood_principle].	+	To have a data flow between nodes it is necessary to decouple data from operations on data. Messages, tokens in data flow parlance, are send from node to node. To have a more robust design inherently non-deterministic, the system should be asynchronous, using the Hollywood principle (stated as "don't call us, we'll call you."[http://en.wikipedia.org/wiki/Hollywood_principle]).

← Older revision		Revision as of 11:44, 14 October 2014
Line 9:		Line 9:

	== Decoupling data from operations on data ==		== Decoupling data from operations on data ==
		+	To have a data flow between nodes it is necessary to decouple data from operations on data. Messages, tokens in dataflow parlance, are send from node to node. To have a more roubust design inherentely non-deterministic, the system should be assynchronous, using the Hollywood principle is stated as "don't call us, we'll call you."[http://en.wikipedia.org/wiki/Hollywood_principle].

← Older revision		Revision as of 11:36, 14 October 2014
Line 7:		Line 7:
	== MS Excel is a reactive programming environment ==		== MS Excel is a reactive programming environment ==
	Continuing from Wikipedia[http://en.wikipedia.org/wiki/Reactive_programming] "A modern spreadsheet program is an example of reactive programming. Spreadsheet cells can contain literal values, or formulas such as "=<math>B1+C1</math>" that are evaluated based on other cells. Whenever the value of the other cells change, the value of the formula is automatically updated."		Continuing from Wikipedia[http://en.wikipedia.org/wiki/Reactive_programming] "A modern spreadsheet program is an example of reactive programming. Spreadsheet cells can contain literal values, or formulas such as "=<math>B1+C1</math>" that are evaluated based on other cells. Whenever the value of the other cells change, the value of the formula is automatically updated."
		+
		+	== Decoupling data from operations on data ==

@@ Line 5: / Line 5: @@
 "In '''reactive programming''', the value of <math>a</math> would be automatically updated based on the new values."
-== MS Excel is a reactive programming environement ==
+== MS Excel is a reactive programming environment ==
 Continuing from Wikipedia[http://en.wikipedia.org/wiki/Reactive_programming] "A modern spreadsheet program is an example of reactive programming. Spreadsheet cells can contain literal values, or formulas such as "=<math>B1+C1</math>" that are evaluated based on other cells. Whenever the value of the other cells change, the value of the formula is automatically updated."