@conference {2022:icsa,
	title = {Web APIs Structures and Data Models Analysis},
	booktitle = {19th IEEE International Conference on Software Architecture (ICSA 2022)},
	year = {2022},
	month = {March},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Honululu, Hawaii},
	abstract = {Microservice architectures emphasize keeping components small, to foster autonomy, low coupling, and independent evolution. In this large-scale empirical study, we measure the size of Web API specifications mined from open source repositories. These APIs are modeled using the OpenAPI Specification (OAS), which, in addition to documenting the offered operations, also contain schemas definitions for the data exchanged with the API request and response message payloads.  This study has as a goal to build empirical knowledge about:  (1) How big and diverse are real-world web APIs both in terms of their operations and data, (2) How different API structures use and reuse schema definitions. By mining public software repositories on Github, we gathered 42,194 valid OAS specifications published between 2014-2021. },
	keywords = {API Analytics, API Size, OpenAPI},
	author = {Souhaila Serbout and Fabio Di Lauro and Cesare Pautasso}
}
@conference {2021:icwe:liquid-wasm,
	title = {WebAssembly Modules as Lightweight Containers for Liquid IoT Applications},
	booktitle = {21st International Conference on Web Engineering (ICWE2021)},
	year = {2021},
	month = {May},
	publisher = {Springer},
	organization = {Springer},
	address = {Biarritz, France},
	abstract = {Going all the way to IoT with web technologies  opens up the door to isomorphic IoT system architectures, which deliver flexible deployment and live migration of code between any device in the overall system. In this vision paper, we propose using WebAssembly to implement lightweight containers and deliver the required portability. Our long-term vision is to use the technology to support developers of liquid IoT applications offering seamless, hassle-free use of multiple devices.},
	keywords = {containers, Internet of Things, IoT, Light-weight containers, liquid software, Web of Things, WebAssemly, WoT},
	author = {Niko M{\"a}kitalo and Tommi Mikkonen and Cesare Pautasso and Victor Bankowski and Paulius Daubaris and Risto Mikkola and Oleg Beletski}
}
@conference {2019:icwe:cornucopia,
	title = {On the Web Platform Cornucopia},
	booktitle = {19th International Conference on Web Engineering (ICWE 2019)},
	year = {2019},
	month = {June},
	pages = {347-355},
	publisher = {Springer},
	organization = {Springer},
	address = {Daejeon, Korea},
	abstract = {The evolution of the Web browser has been organic, with new features introduced on a pragmatic basis rather than following a clear rational design. This evolution has resulted in a cornucopia of overlapping features and redundant choices for developing Web applications. These choices include multiple architecture and rendering models, different communication primitives and protocols, and a variety of local storage mechanisms. In this position paper we examine the underlying reasons for this historic evolution. We argue that without a sound engineering approach and some fundamental rethinking there will be a growing risk that the Web may no longer be a viable, open software platform in the long run.},
	keywords = {Web Engineering; Web Platform},
	doi = {10.1007/978-3-030-19274-7_25},
	author = {Tommi Mikkonen and Cesare Pautasso and Kari Systa and Antero Taivalsaari}
}
@article {2018:ieeesw,
	title = {The Web as a Software Connector: Integration Resting on Linked Resources},
	journal = {IEEE Software},
	volume = {35},
	year = {2018},
	month = {January/February},
	pages = {93 - 98},
	abstract = {The web, seen as a graph of linked resources shared between microservices, can serve as an integration style. It offers unique characteristics and possibilities regarding dataflow, control flow, and other qualities, compared to file transfer, shared databases, remote procedure calls, and asynchronous messaging. Carrying these insights in your toolbox will make you aware of all the options to consider next time you build loosely coupled integrated systems.},
	keywords = {coupling, REST, software architecture},
	doi = {10.1109/MS.2017.4541049},
	url = {http://ieeexplore.ieee.org/document/8239944/},
	author = {Cesare Pautasso and Olaf Zimmermann}
}
@conference {2018:webist,
	title = {Web User Interface Implementation Technologies: An Underview},
	booktitle = {14th International Conference on Web Information Systems and Technologies (WEBIST 2018)},
	year = {2018},
	month = {September},
	pages = {127-136},
	address = {Seville, Spain},
	abstract = {Over the years, the World Wide Web has evolved from a document distribution environment into a rich development platform that can run compelling, full-fledged software applications. However, the programming capabilities of the web browser {\textendash} designed originally for relatively simple scripting tasks {\textendash} have evolved organically in a rather haphazard fashion. Consequently, there are many ways to build applications on the Web today. Depending on one{\textquoteright}s viewpoint, current standards-compatible web browsers support three, four or even five built-in application rendering and programming models. In this paper, we provide an {\textquotedblright}underview{\textquotedblright} of the built-in client-side web application UI implementation technologies, i.e., a summary of those rendering models that are built into the standards-compatible web browser out-of-the-box. While the dominance of the base HTML/CSS/JS technologies cannot be ignored, we foresee Web Components and WebGL gaining popularity as the world moves towards more complex and even richer web applications, including systems supporting virtual and augmented reality.},
	keywords = {Web application architecture},
	doi = {10.5220/0006885401270136},
	url = {http://insticc.org/node/TechnicalProgram/webist/presentationDetails/68854},
	author = {Antero Taivalsaari and Tommi Mikkonen and Kari Systa and Cesare Pautasso}
}
@article {benchflow:2017:icse,
	title = {Workflow Management Systems Benchmarking: Unfulfilled Expectations and Lessons Learned},
	year = {2017},
	month = {May},
	address = {Buenos Aires, Argentina},
	abstract = {Workflow Management Systems (WfMSs) are a type of middleware that enables the execution of automated business processes. Users rely on WfMSs to construct flexible and easily maintainable software systems. Significant effort has been invested into standardising languages for business processes execution, with standards such as the Web Services Business Process Execution Language 2.0 or the Business Process Model and Notation 2.0.
Standardisation aims at avoiding vendor lock-in and enabling WfMS users to compare different systems. The reality is that, despite standardisation efforts, different independent research initiatives show that objectively comparing WfMSs is still challenging. As a result, WfMS users are likely to discover unfulfilled expectations while evaluating and using these systems. In this work, we discuss the findings of two research initiatives dealing with WfMSs benchmarking, presenting unfulfilled expectations and lessons learned concerning WfMSs{\textquoteright} usability, reliability, and portability.  Our goal is to provide advice for practitioners implementing or planning to use WfMSs.},
	keywords = {Lessons Learned, Workflow Management Systems},
	doi = {10.1109/ICSE-C.2017.126},
	author = {Vincenzo Ferme and J{\"o}rg Lenhard and Simon Harrer and Matthias Geiger and Cesare Pautasso}
}
@proceedings {2016:icwe,
	title = {Web Engineering},
	volume = {9671},
	year = {2016},
	month = {June},
	pages = {XXVI, 626},
	publisher = {Springer},
	address = {Lugano, Switzerland},
	keywords = {Web engineering},
	issn = {978-3-319-38790-1},
	doi = {10.1007/978-3-319-38791-8},
	url = {http://icwe2016.webengineering.org},
	author = {Alessandro Bozzon and Philippe Cudr{\'e}-Mauroux and Cesare Pautasso}
}
@proceedings {2016:icwe:workshop,
	title = {Web Engineering Workshops},
	volume = {9881},
	year = {2016},
	month = {June},
	pages = {209},
	publisher = {Springer},
	address = {Lugano, Switzerland},
	keywords = {Web engineering},
	issn = {978-3-319-46962-1},
	doi = {10.1007/978-3-319-46963-8},
	url = {http://icwe2016.webengineering.org},
	author = {Sven Casteleyn and Peter Dolog and Cesare Pautasso}
}
@conference {restws:2009:www,
	title = {Why is the Web Loosely Coupled?  A Multi-Faceted Metric for Service Design},
	booktitle = {18th World Wide Web Conference (WWW2009)},
	year = {2009},
	month = {April},
	pages = {911-920},
	publisher = {ACM},
	organization = {ACM},
	address = {Madrid, Spain},
	abstract = {Loose coupling is often quoted as a desirable property of systems architectures. One of the main goals of building systems using Web technologies is to achieve loose coupling. However, given the lack of a widely accepted definition of this term, it becomes hard to use coupling as a criterion to evaluate alternative Web technology choices, as all options may exhibit, and claim to provide, some kind of "loose" coupling effects. This paper presents a systematic study of the degree of coupling found in service-oriented systems based on a multi-faceted approach. Thanks to the metric introduced in this paper, coupling is no longer a one-dimensional concept with loose coupling found somewhere in between tight coupling and no coupling. The paper shows how the metric can be applied to real-world examples in order to support and improve the design process of service-oriented systems.},
	keywords = {coupling, REST, RESTful Web service interface},
	doi = {10.1145/1526709.1526832},
	author = {Cesare Pautasso and Erik Wilde}
}
