Transactions in content-based publish/subscribe middleware

  • Luis Vargas
  • , Lauri I.W. Pesonen
  • , Ehud Gudes
  • , Jean Bacon

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

    4 Scopus citations

    Abstract

    Content-based publish/subscribe provides a flexible communication model for component interoperation in large-scale environments. In process support systems and other applications that follow an event-based architectural style, the definition of dependencies between interacting components and the notion of all-or-nothing semantics are often needed to ensure reliable inter-component task execution. In this paper we introduce publish/subscribe (P/S) transactions as an abstraction to support these needs in content-based publish/subscribe middleware. A P/S transaction demarcates within an atomic unit-of-work, the production, delivery, and processing of a number of related asynchronous event notifications. A transaction service, provided by the middleware, realises P/S transactions to support the transactional execution of processes on behalf of applications.

    Original languageEnglish
    Title of host publication27th International Conference on Distributed Computing Systems Workshops, ICDCSW'07
    DOIs
    StatePublished - 15 Nov 2007
    Event27th International Conference on Distributed Computing Systems Workshops, ICDCSW'07 - Toronto, ON, Canada
    Duration: 22 Jun 200729 Jun 2007

    Publication series

    NameProceedings - International Conference on Distributed Computing Systems

    Conference

    Conference27th International Conference on Distributed Computing Systems Workshops, ICDCSW'07
    Country/TerritoryCanada
    CityToronto, ON
    Period22/06/0729/06/07

    ASJC Scopus subject areas

    • Software
    • Hardware and Architecture
    • Computer Networks and Communications

    Fingerprint

    Dive into the research topics of 'Transactions in content-based publish/subscribe middleware'. Together they form a unique fingerprint.

    Cite this