The Community for Technology Leaders
Green Image
<p><b>Abstract</b>—The development of complex distributed systems demands for the creation of suitable architectural styles (or paradigms) and related runtime infrastructures. An emerging style that is receiving increasing attention is based on the notion of event. In an event-based architecture, distributed software components interact by generating and consuming events. An event is the occurrence of some state change in a component of a software system, made visible to the external world. The occurrence of an event in a component is asynchronously notified to any other component that has declared some interest in it. This paradigm (usually called “publish/subscribe,” from the names of the two basic operations that regulate the communication) holds the promise of supporting a flexible and effective interaction among highly reconfigurable, distributed software components. In the past two years, we have developed an object-oriented infrastructure called JEDI (Java Event-Based Distributed Infrastructure). JEDI supports the development and operation of event-based systems and has been used to implement a significant example of distributed system, namely, the OPSS workflow management system (WFMS). The paper illustrates the main features of JEDI and how we have used them to implement OPSS. Moreover, the paper provides an initial evaluation of our experiences in using the event-based architectural style and a classification of some of the event-based infrastructures presented in the literature.</p>
Event-based systems, distributed systems, software architectures, workflow, business processes, object-orientation, publish/subscribe middleware.

E. Di Nitto, A. Fuggetta and G. Cugola, "The JEDI Event-Based Infrastructure and Its Application to the Development of the OPSS WFMS," in IEEE Transactions on Software Engineering, vol. 27, no. , pp. 827-850, 2001.
89 ms
(Ver 3.3 (11022016))