Hello, gurus!
So we are building a system with PHP frontend and Oracle as backend.
System will be quite big with possible parallel ~200 users hitting the
system each 3-5 seconds. There will be many updates and selects in the
system and rare deletes.
So we are considering two architectural decisions
- standard Oracle procedures (united in packages of course) with
standard parametrs with standard types. Generally it means if form
consists of 10 input fields then procedure has ~10 parameters (of
course, with some service parameters too). This approach means we have
to make about as many procedures as forms * const. for PHP and Oracle
cooperation.
- second approach - generally we will make 1 or 2 procedures for PHP
and Oracle cooperation. Oracle procedure will have as input and output
parameter XML string that will be formatted in PHP and parsed in Oracle
for form submit and formatted in Oracle and parsed in PHP for form
display. Of course I understand that we have to make all functionality
as well as in 1st appraoch, but these Oracle procedures wouldn't speak
directly with PHP.
So the questions are:
Has anybody made second appraoch in a real aplication? Are there any
suggestions from your experience here?
What traps theoretically we may encounter in second approach?
Have you any idea how much performance will be degraded in second case?
Gints Plivna
Project manager
e-mail: g.plivna_at_softex.lv
WWW: http://www.softex.lv
Please see the official ORACLE-L FAQ:
http://www.orafaq.com
To unsubscribe send email to: oracle-l-request_at_freelists.org
put 'unsubscribe' in the subject line.
--
Archives are at
http://www.freelists.org/archives/oracle-l/
FAQ is at
http://www.freelists.org/help/fom-serve/cache/1.html
Received on Tue Feb 24 2004 - 05:20:35 CST
