Striving for versatility in publish/subscribe infrastructures

Abstract

Publish/subscribe infrastructures are used as the basic communication and integration framework in many application domains. The majority of those infrastructures, however, fall short of mechanisms that allow their customization and configuration to comply with the requirements of those application domains. In other words, they are not versatile enough to support new and evolving requirements demanded by different applications. The YANCEES (Yet ANother Configurable Extensible Event Service) addresses these versatility issues by relying on a combination of plug-in oriented architecture and extensible languages decomposed over different design dimensions of a publish/subscribe infrastructure. We demonstrate our approach, showing how the YANCEES platform can be useful in reducing the customization, extension and implementation effort of different publish/subscribe infrastructures to attend the demands of many application domains.

Continuous Coordination Tools and their Evaluation

“…Whenever a new event-driven application is conceived, developers face two alternatives: build a publish/subscribe infrastructure from scratch, or reuse one of many existing research and industrial systems. A qualitative screening of existing publish/subscribe infrastructures revealed different architectural patterns adopted by industrial and research publish/subscribe infrastructures in the support of the evolving and heterogeneous requirements of different application domains [48]. For example: minimal core, one-size-fits-all, coordination languages and compositional models.…”

“…Most of these patterns are neither extensible nor configurable in the set of features they provide, making their adaptation and reuse a difficult endeavor. This observation motivated the development of YANCEES, which is an extensible and configurable publish/subscribe infrastructure based on plug-ins [47]. As such, our goal in the development of YANCEES was twofold.…”

“…We selected a set of open source infrastructures, one for each category to be compared in a benchmark. These included Siena [6] representing generalized minimal APIs; Sun JavaSpaces [20] representing coordination languages; CORBA Notification Service (or CORBA-NS) [38] representing one-size-fits-all infrastructures, and YANCEES [47] representing flexible compositional infrastructures 3. We selected three feature-rich event-driven application domains as the source of requirements for our study.…”

Understanding the Trade-Offs of Blending Collaboration Services in Support of Contextual Collaboration

“…Notification servers such as Elvin [2] or YANCEES [16] are usually employed as event routing infrastructure to support the development of awareness applications. Elvin provides a relatively simple but optimized set of functionalities, efficiently processing large quantities of events based on content-based routing of tuple-based events.…”

“…We used YANCEES [16] as the notification server because of its ability to be configured with a simple topic-based core, and for having a simple API, similar to Elvin [2]. We used a simple Java-based meeting server from the TeamSpace project [7].…”