Abstract
Distributed event-based systems (DEBS) are networks of computing devices. These systems have been successfully implemented by commercial vendors. Cloud applications depend on message passing and inter-connectivity methods exchanging data and performing inter-process communication. Both DEBS and Clouds need time-coordinated methods of control not dependent on a single time domain. While DEBS have specific implementation languages for complex events, Cloud systems do not. Clouds and DEBS have not yet presented an explicit separation of temporally based event processing from computations. Using a regulated, isomorphic, temporal architecture (RITA), a specific language and separation of temporal event processing from processing computation is achieved. RITA provides a functional programming style for developers using familiar language constructs for integration with existing processing without forcing the developer to work in multiple coding paradigms requiring extensive ``glue code allowing coding paradigms to work together. This paper introduces RITA as a guarded condition-event system that has explicit separation of event processing and computation with constructs allowing integration of time-aware events for multiple time domains found in Cloud or existing distributed computing systems.
Highlights
This paper introduces RITA as a guarded condition-event system that has explicit separation of event processing and computation with constructs allowing integration of time-aware events for multiple time domains found in Cloud or existing distributed computing systems
RITA is an event processing architecture initially developed as a proprietary product in the telecommunications industry between 1998 and 2000 [29] allowing federated and distributed systems to communicate without undue interruption of intensive computing applications
The roots of RITA came from real-time avionics control software [30, 16] and with the current move to have cloud systems handle time critical processing, so RITA is relevant to cloud systems
Summary
RITA is an event processing architecture initially developed as a proprietary product in the telecommunications industry between 1998 and 2000 [29] allowing federated and distributed systems to communicate without undue interruption of intensive computing applications. While the wave forms used to illustrate the canonical events may appear the same as shown in Figures 2.2 and 2.3, note the definite differences in the time element t where, as is explained in Subsection 2.2, a set-at event can transition only once during the lifetime of the system; whereas a transitional event can oscillate between states σ1 and σ2 at any frequency greater than one This temporal difference is very important in constructing a system of events without ambiguity as to the semantics of the intent of a state change. The semantic meaning is compounded based on the frequency of state change and for how many sampling intervals of t the state remains constant This event type has a limited lifetime, albeit the transition between σ1 → σ2 → σ1 can be as long as the system needs it to be, is can appear as a set-at event type, but it is not because it can revert while set-at can not revert to its σ1 state. As shown in transition chain 2.2 each event system can be chained to other event systems
Sign-in/Register to view highlights & summary 
Published Version (
Free)
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
