Sybase Inc has integrated an asynchronous application-to- application message queuing service into its database system to support the increased use of transaction-based applications, especially across the internet and between physically separated networks. The service, which it calls dbQ, provides store and forward message services between Sybase-based database applications, and means users don’t have to wait for each part of a transaction to be completed before they can do other work. Sybase calls it fire and forget. Messages can be routed beyond Sybase environments to non-relational applications running on mainframes via IBM Corp’s MQSeries messaging middleware, which dbQ supports via technology Sybase has licensed from IBM. Sybase will also add support for transactions to Informix and Oracle database applications later in the year. Sybase says the main difference between dbQ and other messaging middleware is that dbQ message queues are integrated directly into the Sybase SQL Server or SQL Anywhere databases. The message queues are supported by the database’s existing back-up, recovery, performance and management tools. dbQ applications can be built from C++, ActiveX or Java components using a variety of development tools. A queue transfer manager offers delivery, notification and priority message options to MQSeries and well as other dbQ servers. Betas are available for Sybase SQL Server and SQL Anywhere on Solaris and NT. Production versions and other Unix ports follow later in the year. MQSeries flag-waver Candle Corp is in the process of cutting a wide-ranging deal to bring its message-based management services to Sybase dbQ customers.
