CumuloNimbo: A highly-scalable transaction processing platform as a service.

One of the main challenges facing next generation Cloud platform services is the need to simultaneously achieve ease of programming, consistency, and high scalability. Big Data applications have so far focused on batch processing. The next step for Big Data is to move to the online world. This shift will raise the requirements for transactional guarantees. CumuloNimbo is a new EC-funded project led by Universidad Politécnica de Madrid (UPM) that addresses these issues via a highly scalable multi-tier transactional platform as a service (PaaS) that bridges the gap between OLTP and Big Data applications.

Client-based Logging: A New Paradigm of Distributed Transaction Management

The proliferation of inexpensive workstations and networks has created a new era in distributed computing. At the same time, non-traditional applications such as computer-aided design (CAD), computer-aided software engineering (CASE), geographic-information systems (GIS), and office-information systems (OIS) have placed increased demands for high-performance transaction processing on database systems. The combination of these factors gives rise to significant challenges in the design of modern database systems. In this thesis, we propose novel techniques whose aim is to improve the performance and scalability of these new database systems. These techniques exploit client resources through client-based transaction management. Client-based transaction management is realized by providing logging facilities locally even when data is shared in a global environment. This thesis presents several recovery algorithms which utilize client disks for storing recovery related information (i.e., log records). Our algorithms work with both coarse and fine-granularity locking and they do not require the merging of client logs at any time. Moreover, our algorithms support fine-granularity locking with multiple clients permitted to concurrently update different portions of the same database page. The database state is recovered correctly when there is a complex crash as well as when the updates performed by different clients on a page are not present on the disk version of the page, even though some of the updating transactions have committed. This thesis also presents the implementation of the proposed algorithms in a memory-mapped storage manager as well as a detailed performance study of these algorithms using the OO1 database benchmark. The performance results show that client-based logging is superior to traditional server-based logging. This is because client-based logging is an effective way to reduce dependencies on server CPU and disk resources and, thus, prevents the server from becoming a performance bottleneck as quickly when the number of clients accessing the database increases.

Transaction management in a replicated and mobile environment

Reports the design of three-level transaction processing model which provides efficient transaction management in a replicated and mobile environment. The model uses a promary/non-primary replication control protocol to enable transaction processing with fast user response time at any distributed site including mobile hosts. A Web-based design with an implementation of a prototype application system shows a concrete example of how to adopt the transaction model over distributed databases.

Grid transaction management and an efficient development kit

Grid transaction management aims at guaranteeing the system consistency in face of various failures in Grid environments. In this paper, we propose a Grid transaction service (GridTS) and design coordination mechanisms for atomic, long-lived and real-time Grid transactions respectively, based on the features of Grid environments. GridTS has the following three advantages. Firstly, it separates the transaction management unit with transaction coordination algorithms so that it can coordinate the above three categories of transactions in a uniform way. Secondly, GridTS can dynamically generate compensating transactions during the long-lived transaction processing. Finally, it provides the programming interfaces similar to traditional distributed transactions. Moreover, we implement a Grid transaction development kit (GridTDK) for application programmers based on our GridTS. We evaluate the feasibility and effectiveness of GridTS by developing an application system using our GridTDK. ©2012 CRL Publishing Ltd.

Seven challenges for RESTful transaction models

The REpresentational State Transfer (REST) architectural style describes the design principles that made the World Wide Web scalable and the same principles can be applied in enterprise context to do loosely coupled and scalable application integration. In recent years, RESTful services are gaining traction in the industry and are commonly used as a simpler alternative to SOAP Web Services. However, one of the main drawbacks of RESTful services is the lack of standard mechanisms to support advanced quality-ofservice requirements that are common to enterprises. Transaction processing is one of the essential features of enterprise information systems and several transaction models have been proposed in the past years to fulfill the gap of transaction processing in RESTful services. The goal of this paper is to analyze the state-of-the-art RESTful transaction models and identify the current challenges.

Performance management of event processing systems

This thesis is a study of performance management of Complex Event Processing (CEP) systems. Since CEP systems have distinct characteristics from other well-studied computer systems such as batch and online transaction processing systems and database-centric applications, these characteristics introduce new challenges and opportunities to the performance management for CEP systems. Methodologies used in benchmarking CEP systems in many performance studies focus on scaling the load injection, but not considering the impact of the functional capabilities of CEP systems. This thesis proposes the approach of evaluating the performance of CEP engines’ functional behaviours on events and develops a benchmark platform for CEP systems: CEPBen. The CEPBen benchmark platform is developed to explore the fundamental functional performance of event processing systems: filtering, transformation and event pattern detection. It is also designed to provide a flexible environment for exploring new metrics and influential factors for CEP systems and evaluating the performance of CEP systems. Studies on factors and new metrics are carried out using the CEPBen benchmark platform on Esper. Different measurement points of response time in performance management of CEP systems are discussed and response time of targeted event is proposed to be used as a metric for quality of service evaluation combining with the traditional response time in CEP systems. Maximum query load as a capacity indicator regarding to the complexity of queries and number of live objects in memory as a performance indicator regarding to the memory management are proposed in performance management of CEP systems. Query depth is studied as a performance factor that influences CEP system performance.

Dimensions of coupling in middleware

It is well accepted that different types of distributed architectures require different degrees of coupling. For example, in client-server and three-tier architectures, application components are generally tightly coupled, both with one another and with the underlying middleware. Meanwhile, in off-line transaction processing, grid computing and mobile applications, the degree of coupling between application components and with the underlying middleware needs to be minimized. Terms such as ‘synchronous’, ‘asynchronous’, ‘blocking’, ‘non-blocking’, ‘directed’, and ‘non-directed’ are often used to refer to the degree of coupling required by an architecture or provided by a middleware. However, these terms are used with various connotations. Although various informal definitions have been provided, there is a lack of an overarching formal framework to unambiguously communicate architectural requirements with respect to (de-)coupling. This article addresses this gap by: (i) formally defining three dimensions of (de-)coupling; (ii) relating these dimensions to existing middleware; and (iii) proposing notational elements to represent various coupling integration patterns. This article also discusses a prototype that demonstrates the feasibility of its implementation.

Identifying services from Legacy batch applications

Transaction processing is a key constituent of the IT workload of commercial enterprises (e.g., banks, insurance companies). Even today, in many large enterprises, transaction processing is done by legacy "batch" applications, which run offline and process accumulated transactions. Developers acknowledge the presence of multiple loosely coupled pieces of functionality within individual applications. Identifying such pieces of functionality (which we call "services") is desirable for the maintenance and evolution of these legacy applications. This is a hard problem, which enterprises grapple with, and one without satisfactory automated solutions. In this paper, we propose a novel static-analysis-based solution to the problem of identifying services within transaction-processing programs. We provide a formal characterization of services in terms of control-flow and data-flow properties, which is well-suited to the idioms commonly exhibited by business applications. Our technique combines program slicing with the detection of conditional code regions to identify services in accordance with our characterization. A preliminary evaluation, based on a manual analysis of three real business programs, indicates that our approach can be effective in identifying useful services from batch applications.

pessimistic predicate/transform model for long running business processes

Many business processes in enterprise applications are both long running and transactional in nature. However, no current transaction model can provide full transaction support for such long running business processes. This paper proposes a new transaction model, the pessimistic predicate/transform (PP/T) model, which can provide full transaction support for long running business processes. A framework was proposed on the enterprise JavaBeans platform to implement the PP/T model. The framework enables application developers to focus on the business logic, with the underlying platform providing the required transactional semantics. The development and maintenance effort are therefore greatly reduced. Simulations show that the model has a sound concurrency management ability for long running business processes.

事务处理技术综述

事务处理技术是保证信息可靠性和一致性的重要技术。事务是具有ACID(atomicity, consistency, isolationanddurability)特性的原子操作序列，它的概念最早来湖泊于数据库管理系统，用来保证应用程序对数据库访问的一致性和可靠性。在早期应用中，商用DBMS系统内部集成的事务管理器提供应用所需的事务处理功能。随着网络技术的发展以及应用需求的变化，以往集中式应用演化发展为网络分布应用，数据和处理分布在不同的计算机上。此时事务管理功能由专门的中间件（例如事务监控器）提供，事务处理技术也发展为分布式事务处理。

移动数据库系统乐观事务处理策略

在移动数据库系统中 ,计算平台的移动性、频繁的断接性以及长事务等特性使得传统的事务处理模式不再适用 .为了解决移动数据库中的事务处理问题 ,提出了一种新的移动事务处理模型——乐观两阶段提交移动事务模型 ( O2 PC-MT) .该模型采用乐观并发控制与两阶段提交协议相结合的方法 ,对移动事务的长事务特性提供了灵活与有效的支持 ;此外 ,该模型允许移动计算机分多次发送事务操作 ,且在事务执行的过程中可以任意移动 ,从而提供了对交互式事务及随意移动性的支持 .实验结果表明 ,与基于两段锁协议及其变形的其它移动事务处理模型相比 ,O2 PC-MT提高了系统的事务吞吐率并改善了系统的总体性能

Logging and Recovery in a Highly Concurrent Database

This report addresses the problem of fault tolerance to system failures for database systems that are to run on highly concurrent computers. It assumes that, in general, an application may have a wide distribution in the lifetimes of its transactions. Logging remains the method of choice for ensuring fault tolerance. Generational garbage collection techniques manage the limited disk space reserved for log information; this technique does not require periodic checkpoints and is well suited for applications with a broad range of transaction lifetimes. An arbitrarily large collection of parallel log streams provide the necessary disk bandwidth.

Analysis of cultural conflict in the development of web-enabled information systems

The advent of the World Wide Web (WWW) and the emergence of Internet commerce have given rise to the web as a medium of information exchange. In recent years, the phenomenon has affected the realm of transaction processing systems, as organizations are moving from designing web pages for marketing purposes, to web-based applications that support business-to-business (WEB) and business-to-consumer (B2C) interactions, integrated with databases and other back-end systems (Isakowitz, Bieber et al., 1998). Furthermore, web-enabled applications are increasingly being used to facilitate transactions even between various business units within a single enterprise. Examples of some of the more popular web-enabled applications in use today include airline reservation systems, internet banking, student enrollment systems in universities, and Human Resource (HR) and payroll systems. The prime motive behind the adoption of web-enabled applications are productivity gains due to reduced processing time, decrease in the usage of paper-based documentation and conventional modes of communication (such as letters, fax, or telephone), and improved quality of services to clients. Indeed, web-based solutions are commonly referred to as customer-centric (Li, 2000), which means that they provide user interfaces that do not necessitate high level of computer proficiency. Thus, organizations implement such systems to streamline routine transactions and gain strategic benefits in the process (Nambisan & Wang, 1999), though the latter are to be expected in the long-term. Notwithstanding the benefits of web technology adoption, the web has ample share of challenges for initiators and developers. Many of these challenges are associated with the unique nature of web-enabled applications. Research in the area of web-enabled information systems has revealed several differences with traditional applications. These differences exist with regards to system development methodology, stakeholder involvement, tasks, and technology (Nazareth, 1998). According to Fraternali (1999), web applications are commonly developed using an evolutionary prototyping approach, whereby the simplified version of the application is deployed as a pilot first, in order to gather user feedback. Thus, web-enabled applications typically undergo continuous refinement and evolution (Ginige, 1998; Nazareth, 1998; Siau, 1998; Standing, 2001). Prototype-based development also leads web-enabled information systems to have much shorter development life cycles, but which, unlike traditional applications, are regrettably developed in a rather adhoc fashion (Carstensen & Vogelsang, 2001). However, the principal difference between the two kinds of applications lies in the broad and diverse group of stakeholders associated with web-based information systems (Gordijn, Akkermans, et al., 2000; Russo, 2000; Earl & Khan, 2001; Carter, 2002; Hasselbring, 2002; Standing, 2002; Stevens & Timbrell, 2002). Stakeholders, or organizational members participating in a common business process (Freeman, 1984), vary in their computer competency, business knowledge, language and culture. This diversity is capable of causing conflict between different stakeholder groups with regards to the establishment of system requirements (Pouloudi & Whitley, 1997; Stevens & Timbrell, 2002). Since, web-based systems transcend organizational, departmental, and even national boundaries, the issue of culture poses a significant challenge to the web systems’ initiators and developers (Miles & Snow, 1992; Kumar & van Dissel, 1996; Pouloudi & Whitley, 1996; Li & Williams, 1999).