Yeast: A General Purpose Event-Action System

Dept. of Software Eng Res., AT&T Bell Labs., Murray Hill, NJ
IEEE Transactions on Software Engineering (Impact Factor: 1.61). 11/1995; 21(10):845 - 857. DOI: 10.1109/32.469456
Source: IEEE Xplore


Distributed networks of personal workstations are becoming the
dominant computing environment for software development organizations.
Many cooperative activities that are carried out in such environments
are particularly well suited for automated support. Taking the point of
view that such activities are modeled most naturally as the occurrence
of events requiring actions to be performed, we developed a system
called Yeast (Yet another Event Action Specification Tool). Yeast is a
client server system in which distributed clients register event action
specifications with a centralized server, which performs event detection
and specification management. Each specification submitted by a client
defines a pattern of events that is of interest to the client's
application plus an action that is to be executed in response to an
occurrence of the event pattern; the server triggers the action of a
specification once it has detected an occurrence of the associated event
pattern. Yeast provides a global space of events that is visible to and
shared by all users. In particular, events generated by one user can
trigger specifications registered by another user. Higher level
applications are built as collections of Yeast specifications. We use
Yeast on a daily basis for a variety of applications, from deadline
notification to software process automation. The paper presents an in
depth description of Yeast and an example application of Yeast, in which
Yeast specifications are used to automate a software distribution
process involving several interdependent software tools

7 Reads
  • Source
    • "For this reason, they were built with a centralized server acting as the broker between the various clients who published and consumed events. One such system that illustrates this architecture is Yeast [5]. As alluded to earlier, Yeast uses a centralized server to manage all clients within the system. "
    [Show abstract] [Hide abstract]
    ABSTRACT: With the growing number of mega services and cloud computing platforms, many industrial organizations are building distributed data centers and are populating them at increasing rates. At the same time, the field of complex event processing(CEP) is gaining popularity as its value is realized for real-time monitoring of these large distributed systems. Traditionally, the CEP system and core event passing infrastructure are created independent of one another. In this paper we propose that including an event based communication system with integrated support for CEP will provide certain benefits at many levels.
    03/2012; 72(3):450-461. DOI:10.1109/COMPSAC.2009.120
  • Source
    • "In a matching tree, leaf nodes represent primitive events and other nodes denote the composition of events. The system--Yeast [10] is an early work to use the tree-based structure. Though GEM [11] clearly expresses complex subscription, the subscription tree can not be shared by other subscription. "
    [Show abstract] [Hide abstract]
    ABSTRACT: With the extension of RFID application, RFID data processing techniques become one of the core techniques. Recently, researchers adopt the event-centric methods to process RFID data and obtain rich semantic information. Complex event processing is a typical data processing technique which becomes the new spotlight of researches. In order to obtain semantic data, in this paper, we propose a complex event detection model to process RFID data. A tree-based complex event detection algorithm which is an improvement to the existed one is realized as the core module in our model. Aimed at improving the detection of non-spontaneous events, we use expected events thus avoid the recursive computation of detection modes and save time cost. The comparative experiments show the algorithm decreases the time complexity of RFID complex event detection. Finally, we implement a production information system based on the complex event detection model and it provides better support for the auto-monitoring of production line.
  • Source
    • "This service was later improved by the CORBA Notification Service [4] [19], which supports event filtering based on event-specific characteristics. The structured event types from CORBA-NS are also used by more sophisticated notification systems, such as READY [9] [8], which is in turn an extension of Yeast [10]. READY provides compound event detection and grouping constructs using separate communication channels and event zones. "
    [Show abstract] [Hide abstract]
    ABSTRACT: Research on client-service interactions in Service-Oriented Architecture mainly focuses on request/response-style messaging. This strategy is based on explicit client-service communication because clients directly invoke op-erations that are exported by the public interface of the ser-vice. Explicit invocation is less suited for reacting to event occurrences. This led to the introduction of implicit invo-cation, a communication strategy that is extensively used in Event-Driven Architectures to signal that a particular situ-ation has occurred. EDA and SOA complement each other because a typical service architecture needs both explicit and implicit invocation. The integration of both paradigms in a single architecture is often referred to as Event-Driven Service-Oriented Architecture. In this paper, we provide an overview of the state of the art of EDSOA. We evaluate the key drivers behind Event-Driven Architecture and we show how concepts from EDA can be integrated into SOA. Then, we focus on a list of chal-lenges, opportunities, and future research directions in cur-rent EDSOAs.
Show more

Similar Publications