TOPS - A new design for transactions in publish/subscribe middleware

Yosef Shatsky, Ehud Gudes

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

3 Scopus citations

Abstract

Publish/subscribe is a common messaging paradigm used for asynchronous communication between applications. Synchronous publish/subscribe middleware exist but are less common because they must address two main performance difficulties, the first being that message dissemination involves larger delays and the second being that resources remain locked for a much longer period of time. Hermes Transaction Service (HTS) is such a middleware, which is capable of treating a group of publications as a transaction. In this paper, we propose a design for a Transactional publish/subscribe middleware, based on HTS. Accordingly, we name the middleware TOPS - Transaction Oriented Publish/Subscribe. We present the detailed functionality and architecture of TOPS and its differences with HTS. To demonstrate the advantages of the TOPS middleware, we describe how different strategies of replication may be implemented all using the middleware proposed.

Original languageEnglish
Title of host publicationProceedings of the 2nd International Conference on Distributed Event-Based Systems, DEBS 2008
Pages201-210
Number of pages10
DOIs
StatePublished - 17 Dec 2008
Event2nd International Conference on Distributed Event-Based Systems, DEBS 2008 - Rome, Italy
Duration: 1 Jul 20084 Jul 2008

Publication series

NameProceedings of the 2nd International Conference on Distributed Event-Based Systems, DEBS 2008

Conference

Conference2nd International Conference on Distributed Event-Based Systems, DEBS 2008
Country/TerritoryItaly
CityRome
Period1/07/084/07/08

Keywords

  • Middleware
  • Publish-subscribe
  • Replication
  • Transactions

ASJC Scopus subject areas

  • Computer Networks and Communications
  • Control and Systems Engineering

Fingerprint

Dive into the research topics of 'TOPS - A new design for transactions in publish/subscribe middleware'. Together they form a unique fingerprint.

Cite this