Design plays a big role. Some banks have massive systems, because all the customer data is in one spot even though customers are spread over several cities and states. To me if you live in City A you conduct most of your transactions in city A and occasionaly on business or holiday you may do business in City B which can be done through a remote procedure. Instead of one big mainframe, why noy have several smaller regional centers. In this area, I am interested in the performance of UvNet, Distributed Files and Remote Procedure calls to handle scalability. Has anyone had experience in this area.
Regards David Jordan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dawn M. Wolthuis Sent: Friday, 23 April 2004 11:50 PM To: [EMAIL PROTECTED] Subject: How far can U2 scale? At what point in the life of application software would it be so large that you could not (or would not want to) support it with your existing UniData or UniVerse database? Is there a point where you would be better served by DB2 or Oracle, for example due to the scale you are working with? I hear people talk about moving way from U2 in order to do ODBC and use standard industry tools (and most find that the grass is not greener for those purposes), but I don't hear about switching because of running into scaling issues. However, we sometimes think of PICK as addressing small-to-mid size businesses and RDBMS folks sometimes think of their products as scaling the best. So, what's the cut-off for U2? Thanks. --dawn Dawn M. Wolthuis Tincat Group, Inc. www.tincat-group.com Take and give some delight today. -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users