Re: Need database/architecture recommendation

Some of the more common choices are:
1) WebLogic application server, using Java for the application development, connecting to Oracle using JDBC.
2) Oracle iAS (formerly OAS). Your development can be in Java or PL/SQL - PL/SQL is a simpler development environment, with development and maintenance being faster and easier than Java. 3) Micrsoft's application server, using ASP pages, written in VB Script. Also a pretty simple development environment, but runs only on NT. Connect to any database using ODBC.

Shops with high volume apps gravitate to the first choice, but the development costs may be higher. For 1,000 transactions a day any of the choices would probably work, although it isn't just a matter of transaction - how many concurrent users are you planning on?

As far as security, that is addressed at several levels -  The application itself should have an application level login/password (like Oracle's MetaLink, or buying a book on Amazon).  You will want a firewall between your app server and your database, to prevent any traffic from hitting your database that does not go through your application server.
 If the data being transmitted is sensitive (i.e. credit card #'s), then you will probably also want to use SSL so that the data being transmitted is encrypted. If you're sending price lists and qty on hand, then SSL is an unnecessary burden.
Firewall software is being patched constantly to protect against new threats (similar to virus software), so it is important to keep everything up to date. Security changes so rapidly, that I would suggest you review that with a consulting company that specializes in network security.

John Alexander
www.SummitSoftwareDesign.com

Maggie <aic_at_foxvalley.net> wrote in message news:39D37CD2.404A0C24_at_foxvalley.net...
> I would like to provide an online ordering system - running scripts or
> queries to a database on our server to provide real-time product
> information (pricing, #in stock, etc...). I am looking for advice on
> selecting the architecture of our system - what database formats
> (msaccess, flat file / ASP, MySQL & PHP) are the most recommended? What
> architecture would you recommend?
>
> I am only familiar with running flat files/Perl [UNIX],
> MSAccess(.mdb)/ASP [NT], and MySql/PHP [UNIX]. I prefer a system that
> can run on Unix and not NT.
>
> I'm also concerned that the database stay out of the hands of my
> competitors. What would you recommend on implementation of security?
> Scripts should access the database via?
>
>
> Maggie
>
Received on Sat Sep 30 2000 - 14:01:43 CEST