transactional publish/subscribe: the proactive multicast of database changes (abstract)  for many years, tibco (the information bus company) has pioneered the use of publish/subscribe---a form of push technology --- to build flexible, real-time loosely-coupled distributed applications. today, publish/subscribe is used by 300 of the world's largest financial institutions, deployed in 6 of the top 10 semiconductor manufacturer' factory floors, utilized in the implementation large-scale internet services like yahoo, intuit, and etrade, and chosen by many of the world's leading corporations as the enterprise infrastructure for integrating disparate applications. in this paper, we will:  contrast the publish/subscribe event-driven interaction paradigm against the traditional demand-driven request-reply interaction paradigm;  explain the concepts of subject-based addressing and self-describing messages, the cornerstones of publish/subscribe;  describe the scalable implementation of publish/subscribe via multicast and broadcast, and the proposed pragmatic general multicast internet standard; and  categorize the qualities of service needed by different kinds of event-driven applications.  today, tibco products support:  reliable delivery for front-office applications which require update notifications only while they are online;  guaranteed delivery for back-office applications that cannot afford to lose messages despite network and application failures; and  transactionally guaranteed delivery for those applications that must update databases, consume messages on one set of subjects, and publish messages on another set of subjects, all within properly bracketed atomic transactions.  three different implementations of transactional publish/subscribe can be found in:  a generic, database independent implementation embodied in tibco's enterprise transaction express (etx) product. etx optimizes two-phase commit for those applications that span a single database and the messaging system by using the last resource manager optimization. it also supports more complicated transactions by playing the role of an xa-compliant resource manager, leaving the transaction coordination to standard-based transaction monitors.  an informix universal server specific extension package called the tibco message blade. this extends the sql language with tibco-provided user defined routines (udrs) for synchronous publish / subscribe operations. in general, udrs can be used inside stored procedures and triggers to publish and consume (potentially complex) structured messages. the need for two-phase commit is finessed by storing messages in the same database that houses application tables.  a bidirectional bridge between oracle 8's advanced queueing (aq) facility and tibco's tib/rendezvous guaranteed message delivery implementation. oracle aq supports enqueue and dequeue operations to queues (actually implemented as oracle tables) that can be performed as part of database transactions. the bridge dequeues from oracle queues and republishes on the information bus. conversely, the bridge subscribes to tib/rendezvous messages and enqueues them to oracle queues for consumption by oracle applications. multiple bridges can be used to route aq messages from one oracle database to another.  arvola chan