Application Integration::Population application pattern::Runtime patterns

Population application pattern::Runtime pattern
(Click a node to get a detailed explanation.)
Design Last Updated: 10-20-2004



A Data Server/Services node is a generic data storage node that provides managed, persistent storage of any type of data and a means to directly access and manipulate that data. The data may be stored in files and accessed through file I/O routines or may be stored in a database with more structured and managed access methods. Although omitted for simplicity of representation, an Application Server/Services node can be substituted for the Data Server/Services node where access to the data is provided through an application API rather than directly to the database management system.

The Population node is a specialized processing node designed and optimized for reading and writing data from/to data stores and transforming the data, often in sophisticated ways, as it passes through. Some Population nodes are further specialized for handling the data under different circumstances, such as efficient throughput of large batches of records that require extensive transformation, or for fast throughput of individual records in near real-time.

Multiple data sources may be involved in the base Population runtime pattern process; and reasonably sophisticated filtering, cleansing, and transformations may occur within the Population function. The main point is that this process can occur in a single step.

What's Next
Next, review product mappings.