Papers in PDF format

All of the above data is streamed in real-time to the Aria.recorder engine, which
intelligently and dynamically transforms this data stream into persistent objects for storage
and analysis purposes. In addition, as the website evolves over time and more or different
data is passed between the client and the server, Aria.monitor is set up to capture that as
well. Aria.monitor is designed to capture all information it sees, and let the Aria.recorder
sort out what information is needed and what information is not. It also takes up virtually
no server resources to run, using less than 50K in disk space.
Aria.recorder
Aria.recorder is an extremely robust data management engine that accepts the data stream
provided by the Aria.monitor, which in turn is capturing all Web Client and Web Server
interactions. Aria.recorder can run on the main Web Server or on a distributed server on a
local or wide area network.
Aria.recorder is designed for high performance and scaleability to manage efficient
processing during peak surges of activity. A single Aria.recorder engine can accept data
streams from multiple Web Servers, each running Aria.monitor. It is a high performance
daemon that is fully scaleable to meet changing volume requirements. During times of
peak activity - if hardware is not capable of handling the load, the recorder creates
optimized backlog files. These files store the update data in an optimized way, such that
when usage/loading relaxes the backlog data can be employed very quickly to update the
database.
Configuration of the recorder can be optimized so that it performs optimally on any
hardware configuration. Larger RAM and disk storage or SMP multi-process servers can
execute the recorder transactions very rapidly, consistent with their superior capabilities
for load handling.
The granularity of data being captured by Aria.recorder is configurable by the site
administrator depending on traffic volumes and specific application needs. Such a filtering
of the data is necessary to avoid persistent storage of data that is not useful. A high
volume site can easily generate up to 400 megabytes per hour, with exponential growth
expected for the future.
Aria.recorder parses the incoming data stream, labels each element for the appropriate
object, and creates the database objects for persistent storage.
Thread Based Architecture
Aria.recorder uses a multi-threaded architecture to make efficient use of processor
resources and is extensible depending on specific site and application needs. It can spawn
new threads to keep up with increasing data loads. The number of threads that can be
running simultaneously is limited only by the available memory and swap space on the
disk.
______________________________________________________________________________
The Aria Architecture Page 17 Andromedia, Inc.
White Paper July 1996