NonStop Systems Introduction for H-Series RVUs

Requirements of Real-Time Solutions
NonStop Systems Introduction for H-Series RVUs—540083-001
2-12
Support for Heavy Transaction Volumes and Mixed
Workloads
applications. In a component-based architecture, real-time applications are assembled
from software modules called components.
An example of a standard component model used in HP real-time solutions is the J2EE
platform. J2EE provides a development environment in which developers use graphical
drag-and-drop techniques to assemble applications from components called beans.
This approach greatly simplifies the development process by relieving developers of
the need to develop the code from scratch. And because the J2EE platform is widely
used throughout the industry, components from different vendors can be mixed and
matched to build applications tailored to a corporation’s needs.
Programs built using standard component models are portable: programs developed
on other platforms, such as Windows or HP-UX, can easily be ported to run on the
NonStop platform. And programming skills are transferable as well; developers do not
need to learn new skills to develop applications for the NonStop system.
Support for Heavy Transaction Volumes and
Mixed Workloads
A real-time solution must be able to support an extremely heavy mixed workload,
including:
•
Hundreds, thousands, or even tens of thousands of events being added per
second
•
Massive random reads in support of real-time inquiries
•
Constant random updating and deleting of information to keep data store current
•
Bulk deletions to remove old data
The real-time model requires a data environment and transaction and query execution
environment in which data flows into and out of the real-time data store with zero (or
low) latency. It must be able to handle constant updating to remain current with the
operational systems. The data is used for making real-time decisions that affect, for
example, customer service. Hundreds of thousands of these decisions, which typically
require subsecond response, might be executed per second. Changes resulting from
real-time applications must be propagated to operational systems to keep the
enterprise synchronized.
For example, several clerks in the same office might be inquiring against an inventory
database and placing sales orders in an order database simultaneously. The
application must process all these transactions simultaneously. At the same time, other
users might be querying the data store for decision support analysis. The system must
be able to support these mixed workloads.
Real-time data might be subject to demand by thousands or even hundreds of
thousands of users. High volume users include call center agents, Web guests, mobile
phone access agents, event and interaction capture agents, EAI agents, and
operations analysis or clerical users.