The Experts below are selected from a list of 9672 Experts worldwide ranked by ideXlab platform
Walter Liebhart - One of the best experts on this subject based on the ideXlab platform.
-
the workflow activity model wamo
Cooperative Information Systems, 1995Co-Authors: Johann Eder, Walter LiebhartAbstract:Workflow technology has not yet lived up to its expectations not only because of social problems but also because of technical problems, like inflexible and rigid process specification and execution mechanisms and insufficient possibilities to handle exceptions. The aim of this paper is to present a workflow model which significantly facilitates the design and reliable management of complex business processes supported by an automatic mechanism to handle exceptions. The strength of the model is its simplicity and the application Independent Transaction facility (advanced control mechanism for workflow units) which guarantees reliable execution of workflow activities.
-
a Transaction oriented workflow activity model
1994Co-Authors: Johann Eder, Walter LiebhartAbstract:The combination of workflow systems and database management systems significantly facilitates the design and reliable management of complex business processes. In this paper we present a high-level workflow activity description language and an advanced Transaction mechanism to design long running activities. The strength of our model is the simplicity of the language and the application Independent Transaction facility which supports highly concurrent and reliable execution of workflow activities.
Johann Eder - One of the best experts on this subject based on the ideXlab platform.
-
the workflow activity model wamo
Cooperative Information Systems, 1995Co-Authors: Johann Eder, Walter LiebhartAbstract:Workflow technology has not yet lived up to its expectations not only because of social problems but also because of technical problems, like inflexible and rigid process specification and execution mechanisms and insufficient possibilities to handle exceptions. The aim of this paper is to present a workflow model which significantly facilitates the design and reliable management of complex business processes supported by an automatic mechanism to handle exceptions. The strength of the model is its simplicity and the application Independent Transaction facility (advanced control mechanism for workflow units) which guarantees reliable execution of workflow activities.
-
a Transaction oriented workflow activity model
1994Co-Authors: Johann Eder, Walter LiebhartAbstract:The combination of workflow systems and database management systems significantly facilitates the design and reliable management of complex business processes. In this paper we present a high-level workflow activity description language and an advanced Transaction mechanism to design long running activities. The strength of our model is the simplicity of the language and the application Independent Transaction facility which supports highly concurrent and reliable execution of workflow activities.
Ricardo Jiménez-peris - One of the best experts on this subject based on the ideXlab platform.
-
Transactional Failure Recovery for a Distributed Key-Value Store
2013Co-Authors: Muhammad Ahmad, Ivan Brondino, Marta Patino-martinez, Bettina Kemme, Ricardo Jiménez-perisAbstract:With the advent of cloud computing, many applications have embraced the ensuing paradigm shift towards modern distributed key-value data stores, like HBase, in order to benefit from the elastic scalability on offer. However, many applications still hesitate to make the leap from the traditional relational database model simply because they cannot compromise on the standard Transactional guarantees of atomicity, isolation, and durability. To get the best of both worlds, one option is to integrate an Independent Transaction management component with a distributed key-value store. In this paper, we discuss the implications of this approach for durability. In particular, if the Transaction manager provides durability (e.g., through logging), then we can relax durability constraints in the key-value store. However, if a component fails (e.g., a client or a key-value server), then we need a coordinated recovery procedure to ensure that commits are persisted correctly. In our research, we integrate an Independent Transaction manager with HBase. Our main contribution is a failure recovery middleware for the integrated system, which tracks the progress of each commit as it is flushed down by the client and persisted within HBase, so that we can recover reliably from failures. During recovery, commits that were interrupted by the failure are replayed from the Transaction management log. Importantly, the recovery process does not interrupt Transaction processing on the available servers. Using a benchmark, we evaluate the impact of component failure, and subsequent recovery, on application performance.
Ricardo Jiḿenez-peris - One of the best experts on this subject based on the ideXlab platform.
-
Transactional failure recovery for a distributed key-value store
Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics), 2013Co-Authors: Muhammad Yousuf Ahmad, Ivan Brondino, Marta Patino-martinez, Bettina Kemme, Ricardo Jiḿenez-perisAbstract:With the advent of cloud computing, many applications have embraced the ensuing paradigm shift towards modern distributed key-value data stores, like HBase, in order to benefit from the elastic scalability on offer. However, many applications still hesitate to make the leap from the traditional relational database model simply because they cannot compromise on the standard Transactional guarantees of atomicity, isolation, and durability. To get the best of both worlds, one option is to integrate an Independent Transaction management component with a distributed key-value store. In this paper, we discuss the implications of this approach for durability. In particular, if the Transaction manager provides durability (e.g., through logging), then we can relax durability constraints in the key-value store. However, if a component fails (e.g., a client or a key-value server), then we need a coordinated recovery procedure to ensure that commits are persisted correctly. In our research, we integrate an Independent Transaction manager with HBase. Our main contribution is a failure recovery middleware for the integrated system, which tracks the progress of each commit as it is flushed down by the client and persisted within HBase, so that we can recover reliably from failures. During recovery, commits that were interrupted by the failure are replayed from the Transaction management log. Importantly, the recovery process does not interrupt Transaction processing on the available servers. Using a benchmark, we evaluate the impact of component failure, and subsequent recovery, on application performance. © IFIP International Federation for Information Processing 2013.
Ivan Brondino - One of the best experts on this subject based on the ideXlab platform.
-
Transactional Failure Recovery for a Distributed Key-Value Store
2013Co-Authors: Muhammad Ahmad, Ivan Brondino, Marta Patino-martinez, Bettina Kemme, Ricardo Jiménez-perisAbstract:With the advent of cloud computing, many applications have embraced the ensuing paradigm shift towards modern distributed key-value data stores, like HBase, in order to benefit from the elastic scalability on offer. However, many applications still hesitate to make the leap from the traditional relational database model simply because they cannot compromise on the standard Transactional guarantees of atomicity, isolation, and durability. To get the best of both worlds, one option is to integrate an Independent Transaction management component with a distributed key-value store. In this paper, we discuss the implications of this approach for durability. In particular, if the Transaction manager provides durability (e.g., through logging), then we can relax durability constraints in the key-value store. However, if a component fails (e.g., a client or a key-value server), then we need a coordinated recovery procedure to ensure that commits are persisted correctly. In our research, we integrate an Independent Transaction manager with HBase. Our main contribution is a failure recovery middleware for the integrated system, which tracks the progress of each commit as it is flushed down by the client and persisted within HBase, so that we can recover reliably from failures. During recovery, commits that were interrupted by the failure are replayed from the Transaction management log. Importantly, the recovery process does not interrupt Transaction processing on the available servers. Using a benchmark, we evaluate the impact of component failure, and subsequent recovery, on application performance.
-
Transactional failure recovery for a distributed key-value store
Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics), 2013Co-Authors: Muhammad Yousuf Ahmad, Ivan Brondino, Marta Patino-martinez, Bettina Kemme, Ricardo Jiḿenez-perisAbstract:With the advent of cloud computing, many applications have embraced the ensuing paradigm shift towards modern distributed key-value data stores, like HBase, in order to benefit from the elastic scalability on offer. However, many applications still hesitate to make the leap from the traditional relational database model simply because they cannot compromise on the standard Transactional guarantees of atomicity, isolation, and durability. To get the best of both worlds, one option is to integrate an Independent Transaction management component with a distributed key-value store. In this paper, we discuss the implications of this approach for durability. In particular, if the Transaction manager provides durability (e.g., through logging), then we can relax durability constraints in the key-value store. However, if a component fails (e.g., a client or a key-value server), then we need a coordinated recovery procedure to ensure that commits are persisted correctly. In our research, we integrate an Independent Transaction manager with HBase. Our main contribution is a failure recovery middleware for the integrated system, which tracks the progress of each commit as it is flushed down by the client and persisted within HBase, so that we can recover reliably from failures. During recovery, commits that were interrupted by the failure are replayed from the Transaction management log. Importantly, the recovery process does not interrupt Transaction processing on the available servers. Using a benchmark, we evaluate the impact of component failure, and subsequent recovery, on application performance. © IFIP International Federation for Information Processing 2013.
