Elastic Business Process Management: State of the Art and Open Challenges for BPM in the Cloud

With the advent of cloud computing, organizations are nowadays able to react rapidly to changing demands for computational resources. Not only individual applications can be hosted on virtual cloud infrastructures, but also complete business processes. This allows the realization of so-called elastic processes, i.e., processes which are carried out using elastic cloud resources. Despite the manifold benefits of elastic processes, there is still a lack of solutions supporting them. In this paper, we identify the state of the art of elastic Business Process Management with a focus on infrastructural challenges. We conceptualize an architecture for an elastic Business Process Management System and discuss existing work on scheduling, resource allocation, monitoring, decentralized coordination, and state management for elastic processes. Furthermore, we present two representative elastic Business Process Management Systems which are intended to counter these challenges. Based on our findings, we identify open issues and outline possible research directions for the realization of elastic processes and elastic Business Process Management.Comment: Please cite as: S. Schulte, C. Janiesch, S. Venugopal, I. Weber, and P. Hoenisch (2015). Elastic Business Process Management: State of the Art and Open Challenges for BPM in the Cloud. Future Generation Computer Systems, Volume NN, Number N, NN-NN., http://dx.doi.org/10.1016/j.future.2014.09.00

AtomServ architecture: Towards internet-scaled service, publish, subscription, and discovery

With the surge of SOA-based infrastructure and applications, increasingly end users and small-medium-enterprises directly participate in the service publish and discovery across the Internet. The recent shutdown of public UDDI exposes critical problems of existing Internet-based service discovery. Hence, public service discovery becomes a central SOA issue. In this paper, we present a light weight service discovery architecture built upon widely-adopted WWW technologies and proven software architectural styles. Firstly, it provides a handy discovery facility for personal web services providers and consumers, who would not be expected to able to use complex UDDI specifications with dedicated endpoint computing capability. Secondly, it widens the adoption of service discovery by allowing simple and uniform web user interfaces (e.g. Internet Explorer7.0 and Firefox1.1) to subscribe and access frequently changing business services. This undoubtedly lowers the entry barrier for end users to play the role of service providers or consumers in a sheer Service-Oriented Environment across the Internet

Performance analysis of a database caching system in a grid environment

Tese de mestrado. Engenharia Informática. Faculdade de Engenharia. Universidade do Porto. 200

Moving social networking applications into the cloud

Social networking applications that are developed using traditional software and architecture have scalability issues. One way to overcome the high cost of scaling social applications is to use Cloud Computing (CC). There are various cloud computing platforms available. One very interesting CC platform is Google App Engine (GAE). This research focuses on using the “free” GAE as a way to re-implement existing social networking applications. The research focuses on how to move social applications into the cloud and on the evaluation of their performance. The thesis investigates the GAE platform, and its features. The study shows how to re-implement a social networking application using GAE cloud with limited code approximately 600 lines and evaluates the scalability of the applications

Survey of NoSQL Database Engines for Big Data

Cloud computing is a paradigm shift that provides computing over Internet. With growing outreach of Internet in the lives of people, everyday large volume of data is generated from different sources such as cellphones, electronic gadgets, e-commerce transactions, social media, and sensors. Eventually, the size of generated data is so large that it is also referred as Big Data. Companies harvesting business opportunities in digital world need to invest their budget and time to scale their IT infrastructure for the expansion of their businesses. The traditional relational databases have limitations in scaling for large Internet scale distributed systems. To store rapidly expanding high volume Big Data efficiently, NoSQL data stores have been developed as an alternative solution to the relational databases. The purpose of this thesis is to provide a holistic overview of different NoSQL data stores. We cover different fundamental principles supporting the NoSQL data store development. Many NoSQL data stores have specific and exclusive features and properties. They also differ in their architecture, data model, storage system, and fault tolerance abilities. This thesis describes different aspects of few NoSQL data stores in detail. The thesis also covers the experiments to evaluate and compare the performance of different NoSQL data stores on a distributed cluster. In the scope of this thesis, HBase, Cassandra, MongoDB, and Riak are four NoSQL data stores selected for the benchmarking experiments

OASIS - Identifying the Core Attributes for RDBMS Alternatives

Since their introduction in the 1970s, relational database management systems have served as the dominate data storage technology. However, the demands of big data and Web 2.0 necessitated a change in the market, sparking the beginning of the NoSQL movement in the late 2000s. NoSQL databases exchanged the relational model and the guaranteed consistency of ACID transactions for improved performance and massive scalability [1]. While the benefits NoSQL provided proved useful, the lack of sufficient SQL functionality presented a major hurdle for organizations which require it to properly operate. It was clear that new RDBMS solutions which did not compromise functionality or scalability were necessary, which has led to the rise of a new class of modern relational database management systems, NewSQL [2]. This paper seeks to identify a consistent set of requirements necessary for an ideal RDBMS substitute. Among these requirements include possessing the features of a modern RDBMS, which includes support of the relational data model and standard ANSI SQL, ACID transactions, and ODBC/JDBC drivers. Additionally, the substitute must address typical RDBMS’ shortcomings in scalability by providing cost-effective scale-out capabilities. These requirements will then be used to filter out existing NoSQL and NewSQL database systems which could serve as viable substitutes to a typical RDBMS