@conference {apiace:2023:europlop,
	title = {API Rate Limit Adoption - A Pattern Collection},
	booktitle = {28th European Conference on Pattern Languages of Programs (EuroPLoP 2023)},
	year = {2023},
	month = {July},
	publisher = {ACM},
	organization = {ACM},
	address = {Kloster Irsee, Germany},
	keywords = {API Design Patterns},
	doi = {10.1145/3628034.3628039},
	url = {https://dl.acm.org/doi/10.1145/3628034.3628039},
	author = {Souhaila Serbout and Amine El Malki and Cesare Pautasso and Uwe Zdun}
}
@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}
}
@conference {2022:sose:ccc,
	title = {Cargo-Cult Containerization: A Critical View of Containers in Modern Software Development},
	booktitle = {16th International Conference on Service-Oriented System Engineering (SOSE 2022)},
	year = {2022},
	month = {August},
	publisher = {IEEE},
	organization = {IEEE},
	address = {San Francisco, USA},
	abstract = {Software is increasingly developed and deployed using containers. While the concept of a container is conceptually straightforward, there are various issues to be considered while using them, ranging from technical details inside containers to the orchestration of containers that jointly form a meaningful application. In recent years, the use of containers has become so prevalent that developers have a tendency to resort to cargo-cult containerization {\textendash} ritual adherence to the use of containers just because so many others are doing the same thing. In this paper, we study advantages and downsides of containers in modern- day software development. We foresee the use of containers to spread into new areas, including IoT systems and embedded devices. At the same time, we caution against indiscriminate use of containers, since excessive containerization can have adverse impacts on software maintenance and overall complexity of a system architecture.},
	keywords = {containers, software architecture},
	author = {Tommi Mikkonen and Cesare Pautasso and Kari Systa and Antero Taivalsaari}
}
@conference {2022:sose:apiace,
	title = {Impact of API Rate Limit on Reliability of Microservices- Based Architectures},
	booktitle = {16th International Conference on Service-Oriented System Engineering (SOSE 2022)},
	year = {2022},
	month = {August},
	publisher = {IEEE},
	organization = {IEEE},
	address = {San Francisco, USA},
	abstract = {Many API patterns and best practices have been
developed around microservices-based architectures, such as Rate
Limiting and Circuit Breaking, to increase quality properties
such as reliability, availability, scalability, and performance.
Even though estimates on such properties would be beneficial,
especially during the early design of such architectures, the real
impact of the patterns on these properties has not been rigorously
studied yet. This paper focuses on API Rate Limit and its impact
on reliability properties from the perspective of API clients. We
present an analytical model that considers specific workload
configurations and predefined rate limits and then accurately
predicts the success and failure rates of the back-end services.
The model also presents a method for adaptively fine-tuning
rate limits. We performed two extensive data experiments to
validate the model and measured Rate Limiting impacts, firstly
on a private cloud to minimize latency and other biases, and
secondly on the Google Cloud Platform to test our model in a
realistic cloud environment. In both experiments, we observed a
low percentage of prediction errors. Thus, we conclude that our
model can provide distributed system engineers and architects
with insights into an acceptable value for the rate limits to
choose for a given workload. Very few works empirically studied
the impact of Rate Limit or similar API-related patterns on
reliability.},
	keywords = {API Analytics},
	author = {Amine El Malki and Uwe Zdun and Cesare Pautasso}
}
@conference {2021:icwe:fullstack,
	title = {Full Stack is Not What It Used to Be},
	booktitle = {21st International Conference on Web Engineering (ICWE2021)},
	year = {2021},
	month = {May},
	publisher = {Springer},
	organization = {Springer},
	address = {Biarritz, France},
	abstract = {The traditional definition of full stack development refers to a skill set that is required for writing software both for the frontend and backend of a web application or site.  In recent years, the scope of full stack development has expanded significantly, though.  Today, a full stack software developer is assumed to master various additional areas especially related to cloud infrastructure and deployment, message brokers and data analytics technologies.  In addition, the emergence of Internet of Things (IoT) and the rapidly spreading use of AI/ML technologies are introducing additional skill set requirements.  In this paper, we discuss the expectations for a modern full stack developer based on our industry observations, and argue that these expectations have significant implications for software and web engineering education.},
	keywords = {Cloud, Education, Internet of Things, IoT, Programmable World, software architecture, software engineering, Web engineering},
	doi = {10.1007/978-3-030-74296-6_28},
	author = {Antero Taivalsaari and Tommi Mikkonen and Cesare Pautasso and Kari Systa}
}
@article {2021:computer,
	title = {Isomorphic Internet of Things Architectures With Web Technologies},
	journal = {Computer},
	volume = {54},
	year = {2021},
	month = {July},
	pages = {69--78},
	abstract = {Internet of Things development needs isomorphic software architectures, in which every kind of device can be programmed with a consistent set of implementation technologies, allowing applications and their components to be statically deployed or dynamically migrated without having to change their shape.},
	keywords = {Internet of Things, Isomorphic Architecture, Web},
	doi = {10.1109/MC.2021.3074258},
	url = {https://ieeexplore.ieee.org/document/9473238},
	author = {Tommi Mikkonen and Cesare Pautasso and Antero Taivalsaari}
}
@inbook {2021:icwe:liquid,
	title = {Towards Seamless IoT Device-Edge-Cloud Continuum},
	booktitle = {Communications in Computer and Information Science},
	volume = {1508},
	number = {ICWE 2021 Workshops},
	year = {2021},
	pages = {82 - 98},
	publisher = {Springer},
	organization = {Springer},
	abstract = {In this paper we revisit a taxonomy of client-side IoT software architectures that we presented a few years ago. We note that the emergence of inexpensive AI/ML hardware and new communication technologies are broadening the architectural options for IoT devices even further. These options can have a significant impact on the overall end-to-end architecture and topology of IoT systems, e.g., in determining how much computation can be performed on the edge of the network. We study the implications of the IoT device architecture choices in light of the new observations, as well as make some new predictions about future directions. Additionally, we make a case for isomorphic IoT systems in which development complexity is alleviated with consistent use of technologies across the entire stack, providing a seamless continuum from edge devices all the way to the cloud.},
	keywords = {Edge Computing, Embedded devices, Internet of Things, Isomorphic software, liquid software, Programmable World, software architecture, software engineering},
	isbn = {978-3-030-92230-6},
	issn = {1865-0929},
	doi = {10.1007/978-3-030-92231-3_8},
	url = {https://link.springer.com/chapter/10.1007/978-3-030-92231-3_8},
	author = {Taivalsaari, Antero and Mikkonen, Tommi and Pautasso, Cesare}
}
@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 {2020:bac:iccs,
	title = {Microservice Disaster Crash Recovery: A Weak Global Referential Integrity Management},
	booktitle = {International Conference on Computational Science},
	year = {2020},
	month = {June},
	address = {Amsterdam, The Netherlands},
	abstract = {Microservices which use polyglot persistence (using multiple data storage techniques) cannot be recovered in a consistent state from backups taken independently. As a consequence, references across microservice boundaries may break after disaster recovery. 
In this paper, we give a weak global consistency definition for microservice architectures and present a recovery protocol which takes advantage of cached referenced data to reduce the amnesia interval for the recovered microservice, i.e., the time interval after the most recent backup, during which state changes may have been lost.},
	keywords = {BAC theorem, Microservices},
	author = {Maude Manouvrier and Cesare Pautasso and Marta Rukoz}
}
@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}
}
@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 {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 {2017:icsa:web,
	title = {Comparing the Built-In Application Architecture Models in the Web Browser},
	booktitle = {1st IEEE International Conference on Software Architecture (ICSA 2017)},
	year = {2017},
	month = {April},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Gothenburg, Sweden},
	abstract = {Depending on one{\textquoteright}s viewpoint, a generic standards-compatible web browser supports three, four or five built-in application rendering and programming models. In this paper, we provide an overview of the built-in client-side web application architectures. 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, Web development, Web engineering},
	author = {Antero Taivalsaari and Tommi Mikkonen and Cesare Pautasso and Kari Systa}
}
@inproceedings {2017:asq:pale,
	title = {Experiences Using an Interactive Presentation Platform in a Functional and Logic Programming Course.},
	year = {2017},
	month = {July},
	publisher = {ACM},
	address = {Bratislava, Slovakia},
	abstract = {Modern constructivist approaches to education dictate active experimentation with the study material and have been linked with improved learning outcomes in STEM fields. During classroom time we believe it is important for students to experiment with the lecture material since active recall helps them to start the memory encoding process as well as to catch misconceptions early and to prevent them from taking root. In this paper, we report on our experiences using ASQ, a Web-based interactive presentation tool in a functional and logic programming course taught at the Faculty of Informatics and Information Technologies at the Slovak University of Technology in Bratislava. ASQ allowed us to collect immediate feedback from students and retain their attention by asking complex types of questions and aggregating student answers in real time. From our experience we identified several requirements and guidelines for successfully adopting ASQ. One of the most critical concerns was how to estimate the time when to stop collecting the students{\textquoteright} answers and proceed to their evaluation and discussion with the class. We also report the students{\textquoteright} feedback on the ASQ system that we collected in the form of the standard SUS questionnaire. 
},
	keywords = {ASQ},
	author = {Vasileios Triglianos and Martin Labaj and Robert Moro and Jakub Simko and Michal Hucko and Jozef Tvarozek and Cesare Pautasso and Maria Bielikova}
}
@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}
}
@inproceedings {wesoa2015,
	title = {From Choreography Diagrams to RESTful Interactions},
	year = {2015},
	month = {November},
	publisher = {Springer},
	address = {Goa, India},
	abstract = {Today, business process management is a key approach to organize work, and many companies represent their operations in business process models. Recently, choreography diagrams have been introduced to represent interactions between business processes, run by different partners. While there is considerable work on using process models during process implementation, there is little work on using choreography models to implement interactions between business processes. In this paper, a novel approach to enhance choreography diagrams by execution information is introduced. The approach is based on the REST architecture style, which is the primary way for interacting systems. Using enhanced choreography diagrams allows us to develop REST-based interactions among business partners in an efficient manner. The approach is illustrated by an example of an accommodation reservation service.},
	keywords = {BPMN Choreography, RESTful conversation},
	author = {Adriatik Nikaj and Sankalita Mandal and Cesare Pautasso and Mathias Weske}
}
@conference {liquid:icwe:2015,
	title = {Towards Liquid Web Applications},
	booktitle = {15th International Conference on Web Engineering (ICWE 2015)},
	year = {2015},
	month = {June},
	pages = {134-143},
	publisher = {Springer},
	organization = {Springer},
	address = {Rotterdam, NL},
	abstract = {As the complexity of rich Web applications grows together with the power and number of Web browsers, the next Web engineering challenge to be addressed is to design and deploy Web applications to make coherent use of all devices. As users nowadays operate multiple personal computers, smart phones, tablets, and computing devices embedded into home appliances or cars, the architecture of current Web applications needs to be redesigned to enable what we call Liquid Software. Liquid Web applications not only can take full advantage of the computing, storage and communication resources available on all devices owned by the end user, but also can seamlessly and dynamically migrate from one device to another continuously following the user attention and usage context. In this paper we address the Liquid Software concept in the context of Web applications and survey to which extent and how current Web technologies can support its novel requirements.},
	keywords = {liquid software, liquid web application, position paper},
	doi = {10.1007/978-3-319-19890-3_10},
	author = {Tommi Mikkonen and Kari Systa and Cesare Pautasso}
}
@inproceedings {sosoa:2011,
	title = {Towards Self-Organizing Service-Oriented Architectures},
	year = {2011},
	month = {July},
	pages = {115-121},
	publisher = {IEEE},
	address = {Washington, DC, USA},
	abstract = {Service-oriented architectures (SOAs) provide a successful model for structuring complex distributed software systems, as they reduce the cost of ownership and ease the creation of new applications by composing existing services. However, currently, the development of service-oriented applications requires many manual tasks and prevailing infrastructure is often based on centralized components that are central points of failure and easily become bottlenecks. In this paper, we promote self-organizing SOA as a new approach to overcome these limitations. Self-organizing SOA integrates research results in the areas of autonomic and service oriented computing. We consider self-organizing features for the whole life-cycle of a service-oriented application, from the creation to the execution, optimization, and monitoring.},
	keywords = {autonomic computing, monitoring, self-organizing service-oriented architecture, service composition, service oriented computing, Web services},
	doi = {10.1109/SERVICES.2011.44},
	author = {Walter Binder and Daniele Bonetta and Cesare Pautasso and Achille Peternier and Diego Milano and Heiko Schuldt and Nenad Stojnic and Boi Faltings and Immanuel Trummer}
}
@proceedings {wsrest2010,
	title = {First International Workshop on RESTful Design (WS-REST 2010)},
	year = {2010},
	month = {April},
	publisher = {ACM},
	address = {Raleigh, NC, USA},
	doi = {http://doi.acm.org/10.1145/1798354.1798375},
	url = {http://portal.acm.org/beta/citation.cfm?id=1798354},
	editor = {Cesare Pautasso and Erik Wilde and Alexandros Marinos}
}
@article {5453330,
	title = {Information Quality in Mashups},
	journal = {Internet Computing},
	volume = {14},
	number = {4},
	year = {2010},
	month = {July-August},
	pages = {14-22},
	abstract = {Modern Web 2.0 applications are characterized by high user involvement: users receive support for creating content and annotations as well as "composing" applications using content and functions from third parties. This latter phenomenon is known as Web mashups and is gaining popularity even with users who have few programming skills, raising a set of peculiar information quality issues. Assessing a mashup{\textquoteright}s quality, especially the information it provides, requires understanding how the mashup has been developed, how its components look alike, and how quality propagates from basic components to the final mashup application.},
	keywords = {component quality, information quality, mashup patterns, mashups, quality metrics, Web 2.0 applications, Web mashups},
	issn = {1089-7801},
	doi = {10.1109/MIC.2010.60},
	author = {Cinzia Cappiello and Florian Daniel and Maristella Matera and Cesare Pautasso}
}
@proceedings {mashups09,
	title = {Third international workshop on web APIs and services Mashups (Mashups{\textquoteright}09)},
	year = {2009},
	pages = {695-696},
	address = {Orlando, Florida},
	keywords = {proceedings, Web mashups},
	doi = {http://doi.acm.org/10.1145/1639950.1639969},
	url = {http://mashup.inf.unisi.ch/mashups09/index.php},
	author = {Cesare Pautasso and Stefan Tai and E. Michael Maximilien}
}
@conference {ccgrid2008,
	title = {Initializing a National Grid Infrastructure Lessons Learned from the Swiss National Grid Association Seed Project},
	booktitle = {8th IEEE International Symposium on Cluster Computing and the Grid (CCGRID 2008)},
	year = {2008},
	month = {May},
	pages = {169-176},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Lyon, France},
	abstract = {In addition to multi-national Grid infrastructures, several countries operate their own national Grid infrastructures to support science and industry within national borders. These infrastructures have the benefit of better satisfying the needs of local, regional and national user communities. Although Switzerland has strong research groups in several fields of distributed computing, only recently a national Grid effort was kick-started to integrate a truly heterogeneous set of resource providers, middleware pools, and users. In the following article we discuss our efforts to start Grid activities at a national scale to combine several scientific communities and geographical domains. We make a strong case for the need of standards that have to be built on top of existing software systems in order to provide support for a heterogeneous Grid infrastructure.},
	keywords = {distributed computing, grid computing, middleware, national grid infrastructure},
	doi = {10.1109/CCGRID.2008.62},
	author = {Nabil Abdennadher and Peter Engel and Derek Feichtinger and Dean Flanders and Placi Flury and Sigve Haug and Pascal Jermini and Sergio Maffioletti and Cesare Pautasso and Heinz Stockinger and Wibke Sudholt and Michela Thi{\'e}mard and Nadya Williams and Christoph Witzig}
}
@proceedings {mashups:2008,
	title = {Introduction: Second International Workshop on Web APIs and Services Mashups (Mashups 2008)},
	volume = {5472},
	year = {2008},
	month = {December},
	pages = {133-135},
	publisher = {Springer},
	address = {Sidney, Australia},
	keywords = {Web mashups},
	doi = {10.1007/978-3-642-01247-1_12},
	author = {Cesare Pautasso and Stefan Tai and E. Michael Maximilien}
}
@article {DBLP:journals/bioinformatics/QuandtHMHMPAL08,
	title = {swissPIT: a novel approach for pipelined analysis of mass spectrometry data},
	journal = {Bioinformatics},
	volume = {24},
	number = {11},
	year = {2008},
	pages = {1416-1417},
	abstract = {The identification and characterization of peptides from tandem mass spectrometry (MS/MS) data represents a critical aspect of proteomics. Today, tandem MS analysis is often performed by only using a single identification program achieving identification rates between 10-50\% (Elias and Gygi, 2007). Beside the development of new analysis tools, recent publications describe also the pipelining of different search programs to increase the identification rate (Hartler et al., 2007; Keller et al., 2005). The Swiss Protein Identification Toolbox (swissPIT) follows this approach, but goes a step further by providing the user an expandable multi-tool platform capable of executing workflows to analyze tandem MS-based data. One of the major problems in proteomics is the absent of standardized workflows to analyze the produced data. This includes the pre-processing part as well as the final identification of peptides and proteins. The main idea of swissPIT is not only the usage of different identification tool in parallel, but also the meaningful concatenation of different identification strategies at the same time. The swissPIT is open source software but we also provide a user-friendly web platform, which demonstrates the capabilities of our software and which is available at http://swisspit.cscs.ch upon request for account.},
	keywords = {bioinformatics, scientific workflow management},
	doi = {10.1093/bioinformatics/btn139},
	url = {http://www.ncbi.nlm.nih.gov/pubmed/18436540},
	author = {Andreas Quandt and Patricia Hernandez and Alexandre Masselot and C{\'e}line Hernandez and Sergio Maffioletti and Cesare Pautasso and Ron D. Appel and Fr{\'e}d{\'e}rique Lisacek}
}
@inbook {116,
	title = {Autonomic Computing for Virtual Laboratories},
	booktitle = {Dependable Systems: Software, Computing, Networks},
	number = {4028},
	year = {2006},
	pages = {211-230},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Virtual laboratories can be characterized by their long-lasting, large-scale computations, where a collection of heterogeneous tools is integrated into data processing pipelines. Such virtual experiments are typically modeled as scientific workflows in order to guarantee their reproduceability. In this chapter we present JOpera, one of the first autonomic infrastructures for managing virtual laboratories. JOpera provides a sophisticated Eclipse-based graphical environment to design, monitor and debug distributed computations at a high level of abstraction. The chapter describes the architecture of the workflow execution environment, emphasizing its support for the integration of heterogeneous tools and evaluating its autonomic capabilities, both in terms of reliable execution (self-healing) and automatic performance optimization (self-tuning).},
	keywords = {autonomic computing, JOpera, scientific workflow management},
	isbn = {3-540-36821-3},
	doi = {10.1007/11808107_10},
	author = {Cesare Pautasso and Win Bausch and Gustavo Alonso},
	editor = {J{\"u}rg Kohlas and Bertrand Meyer and Andr{\'e} Schiper}
}
