The architecture of an active database management system

McCarthy, Dennis R.; Dayal, Umeshwar

doi:10.1145/66926.66946

Cited by 233 publications

(66 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Examples where this field plays a key role are emergency control systems, real-time collaboration, or active databases [47]. Here we collectively refer to this class of systems as eventdriven interaction paradigms (EDIP).…”

Section: Figure 1: Sub-areas Of Event-based Systemsmentioning

confidence: 99%

See 1 more Smart Citation

Deriving a unified fault taxonomy for event-based systems

Hummer

Inzinger

Leitner

et al. 2012

Proceedings of the 6th ACM International Conference on Distributed Event-Based Systems

View full text Add to dashboard Cite

Dependability and fault-tolerance, which are key requirements for business-or safety-critical applications, require explicit knowledge of potential faults that may occur within a system. In contrast to other major research directions, the emerging field of distributed event-based systems is yet lacking a common understanding of faults. In this paper we take a step forward and study potential origins and effects of faults in such systems. Our work on a unified fault taxonomy follows a rigorous methodology. We first identify five core sub-areas in the broader field of event-based systems, and discuss commonalities and differences among them. Then we derive from the existing literature a coherent domain model, which accurately captures the specifics of the different areas. The domain model provides a holistic view and covers both structural and procedural aspects of event-based systems. Based on this model, we elaborate a detailed taxonomy of faults, in line with well-established fault dimensions from dependable and secure computing. The fault taxonomy forms the basis for a comprehensive discussion of fault instances across the five sub-areas of event processing.

show abstract

Section: Figure 1: Sub-areas Of Event-based Systemsmentioning

confidence: 99%

“…The approach provides the expressive power of event-condition-action (ECA) rules [47], a popular method for CEP specification. Our formalization is also in line with the stream transformer definition in [64], since the timestamp is accessible as an event property in our model.…”

Section: Input-output Operator Functionmentioning

confidence: 99%

Deriving a unified fault taxonomy for event-based systems

Hummer

Inzinger

Leitner

et al. 2012

Proceedings of the 6th ACM International Conference on Distributed Event-Based Systems

View full text Add to dashboard Cite

show abstract

“…11 demonstrates another system trigger used to activate event adapters when events arrive. A cursor is declared to retrieve all the event adapters registered to listen to this event in lines [11][12][13][14][15][16]. Then a loop is used to execute each entry in the cursor in lines 18-27.…”

Section: Event Triggersmentioning

confidence: 99%

A Framework for Document-Driven Workflow Systems

Wang

Kumar

2005

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. We propose and demonstrate the feasibility of a framework for document-driven workflow systems that requires no explicit control flow and the execution of the process is driven by input documents. The framework can assist workflow designers to discover the data dependencies between tasks in a process and achieve more efficient control flow design. The framework also provides an architecture to separate the workflow system from application data and facilitate inter-organizational processes. Document-driven workflow systems are more flexible than traditional control flow processes, easier to verify and work better for ad hoc workflows. We also implemented a prototype workflow system using the framework entirely in a RDBMS using Transact-SQL in Microsoft SQL Server 2000. A detailed comparison with control driven workflows has also been done.

show abstract

“…An important difference that characterizes a deductive database system with respect to a relational one is that the former stores not only data, but also rules, that allow additional information to be derived from the data stored into the database. Moreover, a deductive database system offers a uniform, declarative paradigm, based on formal logic, for the static Many proposals for using active rules in databases have appeared, both commercial [3,4,19,26,36] and academic [11,14,18,21,25,30,33,37,38,40,41,42] (the latter usually being more flexible than the former). In order to assign a clear semantics to active rules, several approaches have been proposed to integrate active rules in a deductive framework.…”

Section: Introductionmentioning

confidence: 99%

Active-U-Datalog: Integrating active rules in a logical update language

Bertino

Catania

Gervasi

et al. 1998

Transactions and Change in Logic Databases

View full text Add to dashboard Cite

Abstract. Deductive database technology represents an important step towards the goal of developing highly-declarative database programming languages. In order to make deductive databases a practical technology, deductive rules have to be extended to provide a dynamic behavior. In particular, current applications require not only a support for updates and transactions but also the ability to automatically react to the occurrence of particular events. This is possible by integrating typical deductive rules, whose execution is user-dependent, with active rules, whose execution is event-dependent. Current solutions to this problem are not completely satisfactory. In particular, they often lack a clear semantics, guaranteeing termination, confluence and efficient evaluation. The aim of this paper is to propose a new language for integrating active rules, deductive rules and updates in a uniform logical context. The language we propose is based on the U-Datalog language [9], and extends it with support for active rules, modeled according to the PARK semantics [23]. The resulting language allows the representation of several dynamic aspects, such as transaction execution, reactive behavior and update propagation, in a uniform logical framework, admitting a clear and flexible semantics.

show abstract

The architecture of an active database management system

Cited by 233 publications

References 3 publications

Deriving a unified fault taxonomy for event-based systems

Deriving a unified fault taxonomy for event-based systems

A Framework for Document-Driven Workflow Systems

Active-U-Datalog: Integrating active rules in a logical update language

Contact Info

Product

Resources

About