DTP over Routed Networks

>I'm interested to what extent and how RDBMS and tools are being used over
>routed networks to do distributed transaction processing (DTP). Questions
>that I think are relevant include:
>
>Are there more than terminal sessions (Telnet, VT) being used over routed
>networks in TP (transaction processing) applications?
>
>Is the client displaced from the server over a routed network?

I understand that any separation of components in a distributed design that can be displaced from each other over a LAN can be displaced across router and remote link. However, in a transaction intensive environment (>100 TPS at the RDBMS server) intense traffic through the routed link due to other applications may cause some users to not be able to get access to the DTP application in question. Since TCP/IP and IPX/SPX do not employ a class of service/quality of service construct, how do you ensure access to the mission critical application users?

If its not a problem in your networks, what are the typical transaction loads, remote link speeds and brand/model of routers?

>Are two or more databases, displaced from each other over a routed
>network, contributing to the same transaction processing application? Or,
>are there just mass background database updates being done?
>
>What is the protocol suite?
>
>What is the routing protocol? Whose router is being used?
>
>If the network is TCP/IP-based, how do you ensure that the TP application
>has first use of the bandwidth? Or, is this not a problem? Why?
>
>What question didn't I ask that I should have asked?
>
>If you'll respond my email, I'll summarize, here.
>
>Regards,
 

-- 
                  <> Lee D. Rothstein <> LDR_at_VeriTech.com <>
     <> VeriTech <> 7 Merrymeeting Drive <> Merrimack, NH 03054-2934 <>
                    <> 603-424-2900 <> Fax: 603-424-8549 <>
            <> Information Technology Verification & Leadership <>