The PADRES system is designed for enterprise applications. A sampling of enterprise applications for which PADRES is well-suited are described below.
Supply chain applications manage life-cycle from product purchase order, manufacture, shipping and distribution through resellers and suppliers, to stocking at the retailer, and monitoring sales at the retailer, which drives more product orders, etc. Each stage is triggered by the occurrence of one or more events. For example, the event that the retailer’s stock is empty triggers more product orders, or the event that the product has been manufactured triggers the delivery process.
Job scheduling applications can manage an IT infrastructure (e.g., initiate backups, notify administrators of system failures), maintain customer relations (e.g., send coupons to VIP customers every month, call new customers), etc. Each job (such as emailing an administrator) is triggered by some event (such as a database crash).
Applications to monitor sensors (such as the temperature in various components of an assembly line), or process RFID readings (e.g., shipments entering and leaving a warehouse, or products scanned at a point-of-sale terminal) react to external events (such as a high temperature measurement, or the arrival of a shipment).
In SOA architectures, business processes are built by composing services provided by various departments, vendors, partners or customers. The communication among these distributed components can be modeled as a set of events that trigger the invocation, callback, failure handling, and control flow of the business process.
A wide variety of enterprise applications can also be built using the PADRES system, including business activity monitoring, service level agreement monitoring and management, distributed system management and control, and distributed surveillance.
The common thread in these enterprise applications is that they are inherently event-based. They naturally lend themselves to a content-based routing middleware such as PADRES.