River: an intermediate language for stream processing

Robert Soulé; Martin Hirzel; Buğra Gedik; Robert Grimm

doi:10.1002/spe.2338

River: an intermediate language for stream processing

Robert Soulé, Martin Hirzel, Buğra Gedik, Robert Grimm

Computer Science

Research output: Contribution to journal › Article › peer-review

Abstract

Summary This paper presents both a calculus for stream processing, named Brooklet, and its realization as an intermediate language, named River. Because River is based on Brooklet, it has a formal semantics that enables reasoning about the correctness of source translations and optimizations. River builds on Brooklet by addressing the real-world details that the calculus elides. We evaluated our system by implementing front-ends for three streaming languages, and three important optimizations, and a back-end for the System S distributed streaming runtime. Overall, we significantly lower the barrier to entry for new stream-processing languages and thus grow the ecosystem of this crucial style of programming.

Original language	English (US)
Pages (from-to)	891-929
Number of pages	39
Journal	Software - Practice and Experience
Volume	46
Issue number	7
DOIs	https://doi.org/10.1002/spe.2338
State	Published - Jul 1 2016

Keywords

optimizations
stream processing

ASJC Scopus subject areas

Software

Access to Document

10.1002/spe.2338

Cite this

@article{937f1fef259947ec9db3cee0700a8886,

title = "River: an intermediate language for stream processing",

abstract = "Summary This paper presents both a calculus for stream processing, named Brooklet, and its realization as an intermediate language, named River. Because River is based on Brooklet, it has a formal semantics that enables reasoning about the correctness of source translations and optimizations. River builds on Brooklet by addressing the real-world details that the calculus elides. We evaluated our system by implementing front-ends for three streaming languages, and three important optimizations, and a back-end for the System S distributed streaming runtime. Overall, we significantly lower the barrier to entry for new stream-processing languages and thus grow the ecosystem of this crucial style of programming.",

keywords = "optimizations, stream processing",

author = "Robert Soul{\'e} and Martin Hirzel and Buğra Gedik and Robert Grimm",

note = "Publisher Copyright: Copyright {\textcopyright} 2015 John Wiley & Sons, Ltd.",

year = "2016",

month = jul,

day = "1",

doi = "10.1002/spe.2338",

language = "English (US)",

volume = "46",

pages = "891--929",

journal = "Software - Practice and Experience",

issn = "0038-0644",

publisher = "John Wiley and Sons Ltd",

number = "7",

}

TY - JOUR

T1 - River

T2 - an intermediate language for stream processing

AU - Soulé, Robert

AU - Hirzel, Martin

AU - Gedik, Buğra

AU - Grimm, Robert

PY - 2016/7/1

Y1 - 2016/7/1

N2 - Summary This paper presents both a calculus for stream processing, named Brooklet, and its realization as an intermediate language, named River. Because River is based on Brooklet, it has a formal semantics that enables reasoning about the correctness of source translations and optimizations. River builds on Brooklet by addressing the real-world details that the calculus elides. We evaluated our system by implementing front-ends for three streaming languages, and three important optimizations, and a back-end for the System S distributed streaming runtime. Overall, we significantly lower the barrier to entry for new stream-processing languages and thus grow the ecosystem of this crucial style of programming.

AB - Summary This paper presents both a calculus for stream processing, named Brooklet, and its realization as an intermediate language, named River. Because River is based on Brooklet, it has a formal semantics that enables reasoning about the correctness of source translations and optimizations. River builds on Brooklet by addressing the real-world details that the calculus elides. We evaluated our system by implementing front-ends for three streaming languages, and three important optimizations, and a back-end for the System S distributed streaming runtime. Overall, we significantly lower the barrier to entry for new stream-processing languages and thus grow the ecosystem of this crucial style of programming.

KW - optimizations

KW - stream processing

UR - http://www.scopus.com/inward/record.url?scp=84930535990&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=84930535990&partnerID=8YFLogxK

U2 - 10.1002/spe.2338

DO - 10.1002/spe.2338

M3 - Article

AN - SCOPUS:84930535990

SN - 0038-0644

VL - 46

SP - 891

EP - 929

JO - Software - Practice and Experience

JF - Software - Practice and Experience

IS - 7

ER -

River: an intermediate language for stream processing

Abstract

Keywords

ASJC Scopus subject areas

Access to Document

Other files and links

Fingerprint

Cite this