Databases Reference
In-Depth Information
In the second case, our interest is on some aggregate number, such as our total
liabilities, should we win all the auctions we are bidding on. This requires us to
aggregate results from many events, possibly performing some kind of calculation
on them to provide us with a single KPI that gives an indication to the business of
how things are going. BAM allows us to continuously update this number in
real-time on a dashboard, without the need for continued polling. It also allows
us to trigger alerts, perhaps through e-mail or SMS, or to notify an individual
when a threshold is breached.
In both cases, reports delivered can be customized based on the individual receiving
the report.
BAM architecture
It may seem odd to have a section on architecture in the middle of a chapter
about how to effectively use BAM, but the key to successfully utilizing BAM
is an understanding of how the different tiers relate to each other.
Logical view
The preceding diagram represents a logical view of how BAM operates. Events are
acquired from one or more sources through event acquisition and then normalized,
correlated, and stored in event storage (generally a memory area in BAM that is
backed up to the disk). The report cache generates reports based on events in storage
and then delivers those reports, together with real-time updates through the report
delivery layer. Event processing is also performed on events in storage, and when
defined conditions are met, alerts will be delivered through the alert delivery service.
