@conference {benchflow:2015:icpe,
	title = {On the Road to Benchmarking BPMN 2.0 Workflow Engines},
	booktitle = {6th ACM/SPEC International Conference on Performance Engineering},
	year = {2015},
	month = {January},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Austin, TX, USA},
	abstract = {Workflow Management Systems (WfMSs) provide platforms for delivering complex service-oriented applications that need to satisfy enterprise-grade quality of service requirements such as dependability and scalability. 
In this paper we focus on the case of benchmarking the performance of the core of WfMSs, Workflow Engines, that are compliant with the Business Process Model and Notation 2.0 (<a href="http://www.omg.org/spec/BPMN/2.0/">BPMN 2.0</a>) standard.
We first explore the main challenges that need to be met when designing such a benchmark and describe the approaches we designed for tackling them in the <a href="http://design.inf.usi.ch/research/projects/benchflow">BenchFlow project</a>.
We discuss our approach to distill the essence of real-world processes to create from it processes for the benchmark, and to ensure that the benchmark finds wide applicability.},
	keywords = {BenchFlow, benchmarking},
	doi = {10.1145/2668930.2695527},
	author = {Marigianna Skouradaki and Vincenzo Ferme and Frank Leymann and Cesare Pautasso and Dieter Roller}
}
@conference {www08restsoap,
	title = {RESTful Web Services vs. Big Web Services: Making the Right Architectural Decision},
	booktitle = {17th World Wide Web Conference (WWW 2008)},
	year = {2008},
	month = {April},
	pages = {805-814},
	publisher = {ACM},
	organization = {ACM},
	address = {Beijing, China},
	abstract = {Recent technology trends in the Web Services (WS) domain indicate that a solution eliminating the presumed complexity of the WS-* standards may be in sight: advocates of REpresentational State Transfer (REST) have come to believe that their ideas explaining why the World Wide Web works are just as applicable to solve enterprise application integration problems and to simplify the plumbing required to build service-oriented architectures. In this paper we objectify the WS-* vs. REST debate by giving a quantitative technical comparison based on architectural principles and decisions. We show that the two approaches differ in the number of architectural decisions that must be made and in the number of available alternatives. This discrepancy between freedom-from-choice and freedom-of-choice explains the complexity difference perceived. However, we also show that there are significant differences in the consequences of certain decisions in terms of resulting development and maintenance costs. Our comparison helps technical decision makers to assess the two integration styles and technologies more objectively and select the one that best fits their needs: REST is well suited for basic, ad hoc integration scenarios, WS-* is more flexible and addresses advanced quality of service requirements commonly occurring in enterprise computing. },
	keywords = {architectural decisions, REST, SOAP, Web services},
	doi = {10.1145/1367497.1367606},
	author = {Cesare Pautasso and Olaf Zimmermann and Frank Leymann}
}
