JAAD (Java API for ActiveDatabase) was conceived and created during the development of a WEB-based trading system for a major Wall Street bank. The system used TIBCO/ActiveDatabase adapter for monitoring databases updates, and using real-time notifications for updating in-memory caches.
TIBCO/ActiveDatabase (ADB) allows developers to event-enable databases. Using ADB, applications can set up agents to monitor database tables. When data in a table is modified, the monitoring agent publishes a notification using TIBCO/Rendezvous .
One drawback of the ADB product is that the message structures used to exchange data between applications and ActiveDatabase agents must be built explicitly. In other words, there is no higher level API provided by the product to aid applications developers in constructing ADB requests and in parsing responses (publications).
JAAD accomplishes this goal by providing an intuitive API for constructing requests. Application developers simply use the JAAD classes to construct a request. Once a request has been constructed, the corresponding TIBCO/RV message is retrieved through the API and published for ActiveDatabase agents to process. Similarly, once a response (or publication from an agent monitoring a database table) is received by the application, JAAD can be used to parse the message.
Any framework, by definition, will introduce some processing overhead. This framework was tested extensively and much effort was devoted to ensuring that performance is not compromised. Since this framework was first used to build a mission-critical trading system, suffice to say that the framework does not impose any burden on application performance.