HP Reliable Transaction Router - Manual (Page 35)

RTR Server Types
Authentication
RTR callout servers provide facility-based processing for
authentication. For example, a callout server can enable
verification checks to be carried out on all requests in a given
facility.
Callout servers run on backend or router nodes. They receive a
copy of every transaction either delivered to or passing through
the facility.
Callout servers offer the following advantages:
• The checking code is completely separated from other
application code. The application does not have to be
modified to add an authentication check or logging.
• The check can run in parallel with the database updates;
this can improve response times.
• The check can be run on the router hardware.
Because this technique relies on backing out unauthorized
transactions, it is most suitable when only a small proportion of
transactions are expected to fail the check, so as not to have a
performance impact.
Partition
When working with database systems, partitioning the database
can be essential to ensuring smooth and untrammeled
performance with a minimum of bottlenecks. When you
partition your database, you locate different parts of your
database on different disk drives to spread both the physical
storage of your database onto different physical media and to
balance access traffic across different disk controllers and drives.
For example, in a banking environment, you could partition
your database by account number, as shown in Figure 1–18. A
partition is a part or segment of your database.
Key range
Once you have decided to partition your database, you use key
ranges in your application to specify how to route transactions to
the appropriate database partition. A key range is the range of
data held in each partition. For example, the key range for the
first partition in the bank partitioning example goes from 00001
to 19999.
Introduction 1–23