@conference {liquid:2023:icwe,
	title = {LiquidAI: Towards an Isomorphic AI/ML System Architecture for the Cloud-Edge Continuum},
	booktitle = {23rd International Conference on Web Engineering (ICWE)},
	year = {2023},
	month = {June},
	publisher = {Springer},
	organization = {Springer},
	address = {Alicante, Spain},
	abstract = {A typical Internet of Things (IoT) system consists of a large number of different subsystems and devices, including sensors and actuators, gateways that connect them to the Internet, cloud services, end-user applications and analytics. Today, these subsystems are implemented with a broad variety of programming technologies and tools, making it difficult to migrate functionality from one subsystem to another.  In our earlier papers, we have predicted the rise of \emph{isomorphic} IoT system architectures in which all the subsystems can be developed with a consistent set of technologies.  
In this paper we expand the same research theme to machine learning technologies, highlighting the need to use ML in a consistent and uniform fashion across the entire Cloud-Edge continuum. },
	keywords = {IoT, liquid software},
	author = {Kari Systa and Cesare Pautasso and Antero Taivalsaari and Tommi Mikkonen}
}
@article {2017:jwe:liquid,
	title = {Architecting Liquid Software},
	journal = {Journal of Web Engineering},
	volume = {16},
	year = {2017},
	month = {September},
	pages = {433-470},
	abstract = {The Liquid Software metaphor refers to software that can operate seamlessly across multiple devices owned by one or multiple users. Liquid software applications can take advantage of the computing, storage and communication resources available on all the devices owned by the user. Liquid software applications can also dynamically migrate from one device to another, following the user{\textquoteright}s attention and usage context. The key design goal in Liquid Software development is to minimize the additional efforts arising from multiple device ownership (e.g., installation, synchronization and general maintenance of personal computers, smartphones, tablets, home and car displays, and wearable devices), while keeping the users in full control of their devices, applications and data. In this paper we present the design space for Liquid Software, categorizing and discussing the most important architectural dimensions and technical choices. We also provide an introduction and comparison of two frameworks implementing Liquid Software capabilities in the context of the World Wide Web.
},
	keywords = {design space, liquid software, multi-device programming, software architecture},
	doi = {10.26421/JWE16.5-6},
	url = {http://www.rintonpress.com/journals/jweonline.html$\#$v16n56},
	author = {Andrea Gallidabino and Cesare Pautasso and Tommi Mikkonen and Kari Systa and Jari-Pekka Voutilainen and Antero Taivalsaari}
}
@conference {liquidjs:2016:wicsa,
	title = {On the Architecture of Liquid Software: Technology Alternatives and Design Space},
	booktitle = {13th Working IEEE/IFIP Conference on Software Architecture (WICSA 2016)},
	year = {2016},
	month = {April},
	address = {Venice, Italy},
	abstract = {The liquid metaphor refers to software that operates seamlessly across multiple devices owned by one or multiple users. Liquid software architectures can dynamically deploy and redeploy stateful software components and transparently adapt them to the capabilities of heterogeneous target devices. The key design goal in liquid software development is to minimize the efforts that are related to multiple device ownership (e.g., installation, synchronization and general maintenance of personal computers, smartphones, tablets, home displays, cars and wearable devices), while keeping the users in full control of their devices, applications and data. In this paper we present a design space for liquid software, categorizing and discussing the most important architectural issues and alternatives. These alternatives represent relevant capabilities offered by emerging technologies and deployment platforms that are then positioned and compared within the design space presented in the paper.},
	keywords = {design space, liquid software, liquid.js},
	author = {Andrea Gallidabino and Cesare Pautasso and Ville Ilvonen and Tommi Mikkonen and Kari Systa and Jari-Pekka Voutilainen and Antero Taivalsaari}
}
