Distributed Reactive Programming for Reactive Distributed Systems

Myter, Florian; Scholliers, Christophe; Meuter, Wolfgang De

doi:10.22152/programming-journal.org/2019/3/5

Cited by 12 publications

(8 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The other extreme alternative to our tier-crossing semantics is glitch-freedom in a distributed setting [11,16,18]. In other words, across the distributed reactive program there can never be an observable partial propagation.…”

Section: Total Glitch Freedommentioning

confidence: 99%

“…In the field of distributed reactive programming there are several programming languages or even algorithms that describe systems relevant to our multi-tier implementation of FRP with tiered glitch freedom such as SID-UP [11], DREAM [16] and QPROPd [18].…”

Section: Related Workmentioning

confidence: 99%

“…SID-UP [11], a distributed glitch-free propagation algorithm that minimizes messages compared to DREAM and requires a centralized "lock" that makes the distributed program unable to process more than one propagation at a time. QPROP [18], an 6:25 algorithm that provides distributed glitch-free propagation that does not require a central coordinator for locking.…”

Section: Local Glitch Freedommentioning

confidence: 99%

“…Distributed reactive programming languages [11,16,18] have distributed consistency guarantees and allow distributed FRP propagation without observable partial propagations (glitches). ScalaLoci [35] in particular -a general purpose multi-tier extension of Scala which allows programmers to define their own distribution schemesupports tier-crossing primitives with distributed consistency guarantees.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Gavial: Programming the web with multi-tier FRP

2020

View full text Add to dashboard Cite

Web applications are inherently distributed, and not just because their client and server counterparts run on networked systems. Web applications are written in multiple programming languages and as multiple programs: the server and client programs. In an effort to lower the complexity of the web, multi-tier programming was proposed. In multi-tier programming languages the language and its tooling give support to create web applications as a whole, one program is written in one language.Web applications are also inherently asynchronous. On the server, they constantly process several client requests and in the browser they constantly have to react to input, be it from the user or a server. A technique that can be applied to make such programs easier to understand is functional reactive programming. A functional programming model that models an interactive program as compositions between two primitives, behaviors and events.Developing web applications requires dealing with their distributed nature and the natural asynchronicity of user input and network communication. For facilitating this, different researchers have explored the combination of a multi-tier programming language and functional reactive programming. However, existing proposals take his approach only part of the way. Some parts of the application remain imperative, do not consider network traffic overhead of incremental data, compatibility with common APIs like XMLHttpRequest etc., or they do not consider glitches across network communication (or do but introduce locking or overhead)In this paper, we present Gavial: a design and practical implementation of multi-tier FRP that allows constructing a web application as a functionally reactive program. We propose a novel integration of existing techniques such as solutions to bootstrapping web applications, recursive behaviors for web interfaces, asynchronous FRP and incremental behaviors. As well as novel support for tiered glitch freedom, a compromise between performance and glitch-free evaluation of the distributed FRP program, and a three-tiered system suitable for request-response-style applications as well as user-to-user applications. Gavial automatically runs in request-response (XMLHttpRequest) mode or in websocket mode.After applying a number of old and new ideas to create a practical multi-tier FRP implementation in Gavial, we demonstrate it by building an example and show that it can in fact deal realistically with important practical aspects of building web applications. At the same time, we retain the declarative nature of FRP, where behaviors and events have an intuitive, compositional semantics and a clear dependency structure. ACM CCS 2012Listing 2 Delayed DBehavior object DBehavior { def delayed[A](db: ⇒ DBehavior[A]): Behavior[A] }Returning to CircleRoyale, a type Player represents a player's position, and whether he is alive, attacking or dead. The svg method produces the player's circle and optionally the attacking circle as SVG elements. case class Player(position: Vec2D, attacking: ...

show abstract

Section: Total Glitch Freedommentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Local Glitch Freedommentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Gavial: Programming the web with multi-tier FRP

2020

View full text Add to dashboard Cite

show abstract

“…ReactiveX and similar languages may also suffer from glitches. Naive implementations may produce scenarios where different observers receive different streams of data from the same observable [32].…”

Section: B Reactive Programming à La Reactivexmentioning

confidence: 99%