@phdthesis {2017:phd:lws,
	title = {Liquid stream processing on the web: a JavaScript framework},
	year = {2017},
	month = {November},
	school = {USI},
	type = {PhD},
	address = {Lugano, Switzerland},
	abstract = {The Web is rapidly becoming a mature platform to host distributed applications. Pervasive computing application running on the Web are now common in the era of the Web of Things, which has made it increasingly simple to integrate sensors and microcontrollers in our everyday life. Such devices are of great interest to Makers with basic Web development skills. With them, Makers are able to build small smart stream processing applications with sensors and actuators without spending a fortune and without knowing much about the technologies they use. Thanks to ongoing Web technology trends enabling real-time peer-to-peer communication between Web-enabled devices, Web browsers and server- side JavaScript runtimes, developers are able to implement pervasive Web applications using a single programming language. These can take advantage of direct and continuous communication channels going beyond what was possible in the early stages of the Web to push data in real-time. Despite these recent advances, building stream processing applications on the Web of Things remains a challenging task. On the one hand, Web-enabled devices of different nature still have to communicate with different protocols. On the other hand, dealing with a dynamic, heterogeneous, and volatile environment like the Web requires developers to face issues like disconnections, unpredictable workload fluctuations, and device overload. To help developers deal with such issues, in this dissertation we present the Web Liquid Streams (WLS) framework, a novel streaming framework for JavaScript. Developers implement streaming operators written in JavaScript and may interactively and dynamically define a streaming topology. The framework takes care of deploying the user-defined operators on the available devices and connecting them using the appropriate data channel, removing the burden of dealing with different deployment environments from the developers. Changes in the semantic of the application and in its execution environment may be applied at runtime without stopping the stream flow. Like a liquid adapts its shape to the one of its container, the Web Liquid Streams framework makes streaming topologies flow across multiple heterogeneous devices, enabling dynamic operator migration without disrupting the data flow. By constantly monitoring the execution of the topology with a hierarchical controller infrastructure, WLS takes care of parallelising the operator execution across multiple devices in case of bottlenecks and of recovering the execution of the streaming topology in case one or more devices disconnect, by restarting lost operators on other available devices.},
	keywords = {JavaScript, liquid software, stream processing},
	url = {https://doc.rero.ch/record/306887},
	author = {Masiar Babazadeh}
}
@inproceedings {icwe:2015:rmc:wls,
	title = {Mashup Development with Web Liquid Streams},
	year = {2016},
	pages = {98-117},
	publisher = {Springer},
	address = {Rotterdam, The Netherlands},
	abstract = {Web services such as Twitter and Facebook provide direct access to their streaming APIs. The data generated by all of their users is forwarded in quasi-real-time to any external client requesting it: this continuous feed opens up new ways to create mashups that differ from existing data aggregation approaches, which focus on presenting with multiple widgets an integrated view of the data that is pulled from multiple sources.
Streaming data flows directly into the mashup without the need to fetch it in advance, making it possible to exchange data between mashup components through streaming channels. In this challenge submission we show how streaming APIs can be integrated using a stream processing framework. Mashup components can be seen as stream operators, while the mashup can be defined by building a streaming topology. The mashup is built with \wls, a dynamic streaming framework that takes advantage of standard Web protocols to deploy stream topologies both on Web servers and Web browsers.},
	keywords = {mashup development, rapid mashup challenge, web liquid streams},
	author = {Andrea Gallidabino and Masiar Babazadeh and Cesare Pautasso}
}
@conference {lisa:2015:esocc,
	title = {Decentralized Stream Processing over Web-enabled devices},
	booktitle = {4th European Conference on Service-Oriented and Cloud Computing},
	volume = {9306},
	year = {2015},
	month = {September},
	pages = {3-18},
	publisher = {Springer},
	organization = {Springer},
	address = {Taormina, Italy},
	keywords = {liquid software, stream processing},
	doi = {10.1007/978-3-319-24072-5_1},
	author = {Masiar Babazadeh and Andrea Gallidabino and Cesare Pautasso}
}
@conference {lws:icwe:2015,
	title = {Liquid Stream Processing across Web browsers and Web servers},
	booktitle = {15th International Conference on Web Engineering (ICWE 2015)},
	year = {2015},
	month = {June},
	pages = {24-33},
	publisher = {Springer},
	organization = {Springer},
	address = {Rotterdam, NL},
	abstract = {The recently proposed API definition WebRTC introduced peer-to-peer real time communication between Web browsers, allowing streaming systems to be deployed on browsers in addition to traditional server-side execution environments. While streaming applications can be adapted to run on Web browsers, it remains difficult to deal with temporary disconnections, energy consumption on mobile devices and a potentially very large number of heterogeneous peers that join and leave the execution environment affecting the quality of the stream. In this paper we present the decentralized control approach followed by the Web Liquid Streams (WLS) framework, a novel framework for streaming applications running on Web browsers, Web servers and smart devices. Given the heterogeneity of the deployment environment and the volatility of Web browsers, we implemented a control infrastructure which is able to take operator migration decisions keeping into account the deployment constraints and the unpredictable workload.},
	keywords = {liquid software, stream processing, web liquid streams},
	doi = {10.1007/978-3-319-19890-3_3},
	author = {Masiar Babazadeh and Andrea Gallidabino and Cesare Pautasso}
}
@inproceedings {lisa:wsrest2014,
	title = {A RESTful API for Controlling Dynamic Streaming Topologies},
	year = {2014},
	month = {April},
	address = {Seoul, Korea},
	abstract = {Streaming applications have become more and more dynamic and heterogeneous thanks to new technologies which enable platforms like microcontrollers and Web browsers to be able to host part of a streaming topology. 
A dynamic heterogeneous streaming application should support load balancing and fault tolerance while being capable of adapting and rearranging topologies to user needs at runtime. 
In this paper we present a REST API to control dynamic heterogeneous streaming applications. By means of resources, their uniform interface and hypermedia we show how it is possible to monitor, change and adapt the deployment configuration of a streaming topology at runtime.},
	keywords = {REST, streaming},
	author = {Masiar Babazadeh and Cesare Pautasso}
}
@conference {lisa:wicsa2014,
	title = {The Stream Software Connector Design Space: Frameworks and Languages for Distributed Stream Processing},
	booktitle = {11th Working IEEE/IFIP Conference on Software Architecture (WICSA 2014)},
	year = {2014},
	month = {April},
	address = {Sydney, Australia},
	abstract = {In recent years we witnessed the rise of applications in which data is continuously generated and pushed towards consumers in real time through complex processing pipelines. Software connectors like remote procedure call (RPC) do not fit with the needs of such applications, for which the publish/subscribe and the stream connectors are more suitable. 
This paper introduces the design space of the stream software connector by analyzing recent stream processing engine frameworks and domain specific languages featuring native streaming support. On the one side, we want to classify and compare streaming systems based on a taxonomy derived from the wide range of features they offer (i.e., pipeline dynamicity and representation, load balancing and deployment flexibility).
On the other side, the gaps in the design space we identify point at future research directions in the area of distributed stream processing. 
To do so, we gather valuable architectural knowledge in terms of architectural issues and alternatives, elicited by surveying the most important architectural decisions made by the designers of several representative streaming framework architectures.},
	keywords = {design space, software connector, streaming, survey},
	author = {Masiar Babazadeh and Cesare Pautasso}
}
@article {babazadeh2013www,
	title = {The Atomic Web Browser},
	year = {2013},
	month = {May},
	pages = {217-218},
	address = {Rio de Janeiro, Brazil},
	abstract = {The Atomic Web Browser achieves atomicity for distributed transactions across multiple RESTful APIs. Assuming that the participant APIs feature support for the Try-Confirm/Cancel pattern, the user may navigate with the Atomic Web Browser among multiple Web sites to perform local resource state transitions (e.g., reservations or bookings). Once the user indicates that the navigation has successfully completed, the Atomic Web browser takes care of confirming the local transitions to achieve the atomicity of the global transaction.},
	keywords = {REST, REST transactions, try-confirm-cancel, Web engineering},
	url = {http://dl.acm.org/citation.cfm?id=2487788.2487899},
	author = {Cesare Pautasso and Masiar Babazadeh}
}
