To program or not to program that is the question!
Date: Wed, 04 Nov 1998 17:27:14 -0600
Message-ID: <3640E2D2.D10423CC_at_digivis.com>
Can anyone give me a run down on what you feel is the primary differences in the design of a project between vendor based propritary API's (ie like PL-SQL, stored procedures etc.), and an open design that works everywhere on the network no matter where the data is?
I would like opinions as to what the appropriate issues are just to reassure myself I am not living in a dream world.
:)
I am interested in two things really:
#1 When and when it is not appropriate to do proprietary development
using vendore developed API's, for web sites.
#2 The idea that, ODBC and related data sources and databases should be
accessed and treated only through open interfaces such as CORBA and ODBC
data sources, no matter how big the application. (ie with the belief
that building multi-tiered distributed data access servers is easier if
you stick with the standards, and easier to move or deploy on future
platforms, software and hardware).
#3 In the cases of work that you do, how many times would use say it
would call for a proprietary solution from the vendor, in that if you
moved the web site a major rewrite would have to be done?
I believe that these overide performance issues when every 4 months, computer prices drop by as much as 15% in one jump and that it is not cost effective to embrace proprietary API's for performance reasons to make the web application scale. Noticed I am talking about web applications.
That is my belief, how many of you share that?
-Gregory
-gcarter_at_digivis.com
Received on Thu Nov 05 1998 - 00:27:14 CET