Reactors: A data-oriented synchronous/asynchronous programming model for distributed applications

John Field, Maria Cristina Marinescu, Christian Stefansen

Research output: Indexed journal article Articlepeer-review

11 Citations (Scopus)

Abstract

Our aim is to define the kernel of a simple and uniform programming model-the reactor model-which can serve as a foundation for building and evolving internet-scale programs. Such programs are characterized by collections of loosely-coupled distributed components that are assembled on the fly to produce a composite application. A reactor consists of two principal components: mutable state, in the form of a fixed collection of relations, and code, in the form of a fixed collection of rules in the style of Datalog. A reactor's code is executed in response to an external stimulus, which takes the form of an attempted update to the reactor's state. As in classical process calculi, the reactor model accommodates collections of distributed, concurrently executing processes. However, unlike classical process calculi, our observable behaviors are sequences of states, rather than sequences of messages. Similarly, the interface to a reactor is simply its state, rather than a collection of message channels, ports, or methods. One novel feature of our model is the ability to compose behaviors both synchronously and asynchronously. Also, our use of Datalog-style rules allows aspect-like composition of separately-specified functional concerns in a natural way.

Original languageEnglish
Pages (from-to)168-201
Number of pages34
JournalTheoretical Computer Science
Volume410
Issue number2-3
DOIs
Publication statusPublished - 6 Feb 2009
Externally publishedYes

Keywords

  • Actors
  • Asynchronous programming
  • Datalog
  • Distributed programming
  • Reactors
  • Synchronization
  • Synchronous programming

Fingerprint

Dive into the research topics of 'Reactors: A data-oriented synchronous/asynchronous programming model for distributed applications'. Together they form a unique fingerprint.

Cite this